Medianet Reference Guide - Cisco
Medianet Reference Guide - Cisco
Medianet Reference Guide - Cisco
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 6<br />
<strong>Medianet</strong> Management and Visibility Design Considerations<br />
Application-Specific Management Functionality<br />
Table 6-4<br />
<strong>Cisco</strong> TelePresence Application-Specific Management Functionality (continued)<br />
<strong>Cisco</strong> TelePresence<br />
Multipoint Switch<br />
<strong>Cisco</strong> TelePresence<br />
System Endpoint<br />
Fault management • The <strong>Cisco</strong> TelePresence Multipoint Switch provides limited fault<br />
management capabilities. The web-based GUI interface can display errors<br />
and warnings for scheduled and non-scheduled meetings, as well as system<br />
errors.<br />
Configuration<br />
management<br />
Performance<br />
management<br />
Security<br />
management<br />
• The <strong>Cisco</strong> TelePresence Multipoint Switch web-based GUI provides<br />
device/element management capabilities, in that the configuration of the<br />
<strong>Cisco</strong> TelePresence Multipoint Switch itself is accomplished through the<br />
GUI. Limited configuration support of the <strong>Cisco</strong> TelePresence Multipoint<br />
Switch is available via an SSH CLI as well.<br />
• The <strong>Cisco</strong> TelePresence Multipoint Switch web-based GUI also provides the<br />
interface for administrators and meeting schedulers to configure static and<br />
ad hoc TelePresence meetings.<br />
• The <strong>Cisco</strong> TelePresence Multipoint Switch web-based GUI provides<br />
centralized call statistics for multipoint calls, including SLA parameters such<br />
as bit rates, latency, drops, jitter, and so on, per <strong>Cisco</strong> TelePresence System<br />
endpoint.<br />
• The <strong>Cisco</strong> TelePresence Multipoint Switch web-based GUI also provides<br />
historical statistics for <strong>Cisco</strong> TelePresence Multipoint Switch resources<br />
including CPU utilization, traffic load per interface, packet discards, TCP<br />
connections, memory, and disk usage.<br />
• The <strong>Cisco</strong> TelePresence Multipoint Switch web-based GUI provides the<br />
interface for configuration of the security requirements for static and ad hoc<br />
TelePresence meetings.<br />
• Access control to the <strong>Cisco</strong> TelePresence Multipoint Switch is via the local<br />
database with three roles: administrator, meeting scheduler, or diagnostic<br />
technician.<br />
Fault management • The <strong>Cisco</strong> TelePresence System web-based GUI and SSH interfaces both<br />
provide device/element management capabilities, including a view of the<br />
system status, as well as diagnostics that can be used to troubleshoot the<br />
camera, microphone, and display components of the <strong>Cisco</strong> TelePresence<br />
System endpoint.<br />
Configuration<br />
management<br />
• SIP Message log files accessed through the <strong>Cisco</strong> TelePresence System<br />
web-based GUI can be used to troubleshoot SIP signaling between the<br />
<strong>Cisco</strong> TelePresence System endpoint and <strong>Cisco</strong> Unified Communications<br />
Manager.<br />
• Additional <strong>Cisco</strong> TelePresence System log files can be collected and<br />
downloaded via the web-based GUI to provide system-level troubleshooting<br />
capabilities.<br />
• Status of peripheral devices (cameras, displays, microphones, and so on) can<br />
be accessed centrally via SNMP through the CISCO-TELEPRESENCE-MIB.<br />
• The <strong>Cisco</strong> TelePresence System web-based GUI and SSH interfaces both<br />
provide information regarding current hardware and software versions and<br />
current configuration of the <strong>Cisco</strong> TelePresence System endpoint. Limited<br />
configuration is done on the <strong>Cisco</strong> TelePresence System endpoint itself. Most<br />
of the configuration is done via the <strong>Cisco</strong> Unified Communications Manager<br />
Administrator web-based GUI.<br />
OL-22201-01<br />
<strong>Medianet</strong> <strong>Reference</strong> <strong>Guide</strong><br />
6-69