9.2(1)SU1 OL

Transcription

1 Prerequisites, page 1 workflow, page 2 architecture considerations, page 2 Deployment model considerations, page 3 for Large PoD and Small PoD, page 4 for Micro Node, page 8 Prerequisites Before you plan the service assurance subsystem for your Cisco HCS installation, make sure that you: Review and have access to the Solution Reference Network Design for Cisco Hosted Collaboration Solution. Review and have access to the Cisco Hosted Collaboration Solution Assurance Reference Guide. Complete the actions outlined in previous sections of this guide including: Initial system requirements and planned growth Data center requirements Licensing Customer premise equipment Service fulfilment requirements OL

2 workflow workflow architecture considerations As you develop your plan for service assurance consider these four key aspects to consider when building out this plan: Domain management management (Prime Central for HCS Assurance). (Not available with Micro Node deployments.) The Northbound Interface (NBI) to your OSS/BSS Interfaces to the Cisco Hosted Collaboration Fulfilment system Domain management considerations Your domain management abstracts performance and fault management information for a number of components including Cisco Prime Unified Operations Manager, Cisco Prime Unified Service Monitor, Cisco Unified Computing System Monitor, and vcenter. Domain managers also discover topology and relationships between components within its domain and provide diagnostics and tracing tools to assist with troubleshooting within the technology domain. management considerations The Cisco HCS service assurance subsystem includes fault and performance management with a major focus on fault management. Key service assurance functionality includes the following: Event normalization* Event enrichment* Event de-duplication* Prime Central dashboard* Single normalized northbound interface (NBI)* Cross-launch capabilities to service assurance domain managers for diagnostics and detailed troubleshooting* Integration with the Shared Data Repository 2 OL

3 Deployment model considerations Monitoring of the Cisco HCS auxiliary applications and management system Root-cause analysis and service-impact analysis support* Note *Not available with Micro Node. management includes: Collection (Event Collector) Modelling (Service Visualizer, leveraging dependency model in HCM-F) Correlation and impact analysis (Event Correlation Engine and Service Visualizer) Presentation (Portal) Collection (Infrastructure Monitoring) Northbound interface to OSS/BSS systems considerations The Northbound interface to OSS/BSS systems is a key aspect of service assurance as it provides an interface between the Service Assurance manager layer and MSP systems such as trouble ticketing, and manager of managers (MoM). Its functions include delivering enriched events to MSP systems regardless of the component or device manager from which the event originated. This interface also provides web services (WS) API and a CLI interface that allows operators to query the service assurance system to gather additional details about events or historical data. Interface to HCM-F considerations When planning, the relationship between service assurance and service fulfilment is a key relationship to consider. Key functions of this relationship are: To provide a source of information about services and device inventory and relationships used by service assurance to build dependency models needed for root-cause and service impact analysis. To perform programmable customer on-boarding and provisioning of the service assurance system. To interact with the Shared Data Repository (SDR) in HCM-F to extract information to perform functions such as root-cause analysis, service impact analysis, event correlation, and event enrichment. To host services that perform automatic configuration functions of Domain Managers and devices based on information stored on the SDR. Deployment model considerations Earlier in the planning process you determined whether you require a Large PoD, Small PoD, or Micro Node HCS deployment. This decision is fundamental to planning for service assurance. In Large and Small PoD deployments, Prime Central for HCS is available for fault and alarm management, with Micro Node deployments Prime Central for HCS is not available. With Micro Node you must use Cisco Unified Operations Manager, Cisco Unified Service Manager, and Cisco vcenter directly. Other features that are not available with Micro Node include: Data center interface monitoring OL

4 for Large PoD and Small PoD UCS Manager There is no integration with your OSS/BSS. We do not recommend integration where partners are connecting directly to DM. If you determine that this functionality is required, consider moving to a Small PoD implementation where Prime Central for HCS is available. Ensure that you performed the following steps: Cisco Unified Operations Manager OVA sizing is complete. You have the necessary Cisco Unified Operations Manager license files. You know the number of customers, endpoints, and devices required. You know the port and protocol requirements for Cisco Unified Operations Manager and Prime Central for HCS if you are planning for a Large PoD or Small PoD deployment. You know the Cisco Unified Operations Manager port and protocol requirements if you are planning for a Micro Node deployment. for Large PoD and Small PoD If the previous steps in the planning process have resulted in the decision to implement a Large or Small PoD deployment see the following topics. management with Prime Central for HCS Assurance For Large and Small PoD implementations Prime Central for HCS Assurance is a required component. Cisco Prime Central for HCS Assurance is used in the Cisco Hosted Collaboration Solution and interacts with the Shared Data Repository on the Hosted Collaboration Mediation Fulfillment (HCM-F) system to collect information about customers, clusters, applications, and data center components. Prime Central for HCS Assurance includes the following components: Infrastructure Monitor Event Collector Correlation Engine Service Visualizer Prime Central portal For more details on these components and their functions, see the Cisco Hosted Collaboration Solution Assurance Reference Guide 9.2(1) SU1. Prime Central for HCS Assurance monitors the following domain managers: Cisco Prime Unified Operations Manager and Cisco Prime Unified Service Monitor vcenter Cisco Unified Computing System Manager (UCS Manager) 4 OL

5 Estimate Prime Central for HCS Assurance scale numbers Data center interface monitoring is an available though optional component beginning with release Other planning considerations: When planning note that Prime Central for HCS Assurance uses the Red Hat Enterprise Linux 5.5 (64-bit) as its operating system. For more information about technical requirements for Prime Central for HCS Assurance, see the Prime Central for HCS Installation Guide. Northbound Interfaces are via Web Services API and SNMP gateway. For provisioning customers and devices are added through HCM-F. For licensing Prime Central for HCS license is included in HCS Management license. No license file is needed. For installation five VMs are created from OVA. Cisco recommends that Prime Central for HCS be installed in the management VLAN. Note A single instance of Prime Central for HCS Assurance can monitor multiple data centers and supports both Small and Large PoD deployment models. See the Data Center requirements section of this document for more information. Estimate Prime Central for HCS Assurance scale numbers HCS was tested in a simulated environment with 500 Customers, 3000 UC Applications and events sustained at five per second. Due to lab constraints, real-world solution testing was performed with 151 customers, 282 UC Clusters and 470 UC Applications. Data center interface monitoring considerations If using data center interface monitoring (formerly DCNM bypass), plan to set up SNMP traps to be sent directly to Prime Central for HCS Assurance for such components as: Cisco Nexus 1000V Cisco Nexus 7000 Cisco MDS For more information on data center interface monitoring see Cisco Hosted Collaboration Solution Assurance Reference Guide 9.2(1). When taking overall monitoring considerations into account, be aware that Cisco Prime Unified Operations Manager monitors and evaluates the current status of both the IP communications infrastructure and the underlying transport infrastructure in your network. See the Compatibility Matrix for Cisco Hosted Collaboration Solution and the Supported Devices and Interoperable Software Table for Cisco Prime Unified Operations Manager 9.0 for more information. For a list of which devices CUOM supports in an HCS environment see the Cisco Hosted Collaboration Solution Assurance Reference Guide. OL

6 Determine if Northbound Interface will be integrated with your OSS/BSS Determine if Northbound Interface will be integrated with your OSS/BSS As a planner you must understand that Prime Central for Hosted Collaboration Solution Assurance Northbound Interface (NBI) provides a normalized interface between the Cisco HCS service assurance (SA) system and service-provider Northbound systems. The NBI eases integration of the HCS system with the existing managed service provider OSS/BSS systems. This single normalized Northbound interface provides the following: Forward normalized, enriched, and correlated fault messages Support for SNMP traps and WebServices APIs Notification criteria and policies Event retrieval from archived database Multiple Northbound destination support With this in mind, you will need to decide whether or not to integrate Cisco HCS SA with your OSS/BSS. Prime Central for HCS Assurance supports two Northbound interfaces: SNMP Notifications Prime Central for HCS supports SNMP Trap Notifications. SNMP listeners are added, updated, or removed by WebServices API. WebServices API Prime Central for HCS supports a number of WebServices APIs including authenticate, getactiveevent, getoperationaldata, subscribe, and unsuscribe. You will need to plan for supporting SNMP trap notifications and have the ability to work with APIs to set up the appropriate web services. To set up the NBI to receive events from Prime Central for HCS, you must configure a trap receiver. You can configure the trap receiver two ways: Use the Web Services API Run the Python script: pc4hcs_nbi_client.py on the Prime Central for HCS Server. The script is locatedin the directory /opt/pc4hcs_nbi_client/. Note Five NBI destinations are supported. Each destination can have its own filter. For more details about the NBI see the Prime Central for Cisco Hosted Collaboration Solution Programmer Guide at NAT planning considerations If this is an HCS-LE deployment (single customer only), implementing a NAT between your management applications and Unified Communications applications is not required. Be aware that if a NAT is implemented in this scenario that the Cisco Unified Operations Manager synthetic call feature will not be available. 6 OL

7 Provisioning considerations Provisioning considerations When you are planning an HCS installation, provisioning is an important consideration. Determine if auto or manual provisioning will be used. Auto-provisioning of customers and services is available using HCM-F as opposed to manual provisioning. For the Cisco Prime Unified Operations Manager to monitor Unified Communications applications and customer equipment devices, these devices must be configured with event destinations (SNMP trap, syslog, or RTMT API) to the correct Prime Unified Operations Manager. The Cisco HCS Provisioning Adapter (CHPA) service automatically configures event destinations on the Cisco Unified Communications Manager. You must manually set up other applications and devices to forward events to the correct Prime Unified Operations Manager. Estimate the number of Prime Unified Operations Manager and Prime Unified Service Monitor The Cisco Prime Unified Operations Manager is a domain manager that provides monitoring and diagnostics for Cisco HCS Unified Communications applications and devices. Cisco Prime Unified Service Monitor monitors active calls and provides near real-time notification when the voice quality of a call fails to meet a user-defined quality threshold. Cisco recommends installation of both Cisco Prime Unified Operations Manager and Cisco Prime Unified Service Monitor on the same VM. Cisco Prime Unified Operations Manager and Cisco Prime Unified Service Monitor send events to Prime Central for HCS for further analysis. Multiple instances of the Cisco Prime Unified Operations Manager and Service Monitor can be deployed. Multiple OVAs are supported for different capacity requirements. Each instance of the application can support up to 50 customers. There are four Cisco Prime Unified Operations Manager/Cisco Prime Unified Service Monitor OVAs. The OVA you select depends on your deployment. You can deploy multiple Cisco Prime Unified Operations Manage/Cisco Prime Unified Service Monitor instances: Cisco Prime Unified Operations Manager/Cisco Prime Unified Service Monitor OVA phones and 300 IP devices. Cisco Prime Unified Operations Manager/Cisco Prime Unified Service Monitor OVA phones and 1000 IP devices. Cisco Prime Unified Operations Manager/Cisco Prime Unified Service Monitor OVA phones and 2500 IP devices. Cisco Prime Unified Operations Manager/Cisco Prime Unified Service Monitor OVA phones and 2500 IP devices. Procedure Step 1 Step 2 Using the compatibility matrix, estimate the number of Cisco Unified Operation Managers and Cisco Unified Service Monitors required for your system. The compatibility matrix is at Compatibility matrix. Estimate your virtual machine requirements by referring to: Unified Communications Virtualization Downloads (including OVA/OVF Templates). OL

8 Plan to acquire Prime Unified Operations Manager license files Plan to acquire Prime Unified Operations Manager license files As a part of service assurance planning, be sure to acquire the necessary Cisco Prime Unified Operations Manager license files. Note that Prime Central for HCS Assurance does not require a license file. Determine required bandwidth Bandwidth considerations are particularly relevant when considering a split data center with on-premise equipment. For more information on bandwidth considerations, see the Data center requirements chapter. Determine necessary ports/protocols requirements For details on ports and protocols see the System Security chapter in thesolution Reference Network Design Guide for Cisco Hosted Collaboration Solution 9.2(1) SU1. Cisco Unified Border Element naming considerations When planning for service assurance, creating and following a standard naming convention can simplify troubleshooting in the future. For example, use a convention such as Customer name, Cluster ID, Interface ID. Using this convention a name would look like PSTN_CustA_CUCM1_1. Following the naming convention and creating unique names allows for quick identification of the trouble spot and speeds fault diagnosis. for Micro Node If the previous steps in the planning process resulted in the decision to implement a Micro Node deployment be aware that: Prime Central for HCS is not available. Data center interface monitoring is not available. UCS Manager is not available. Event normalization is not available. Event enrichment is not available. Prime Central Dashboard is not available. Single normalized northbound interface (NBI) is not available. Cross-launch capabilities to service assurance domain managers for diagnostics and detailed troubleshooting is not available. Root-cause analysis (RCA) and service-impact analysis (SIA) support is not available. 8 OL

9 for Micro Node There is no integration with your OSS/BSS. We do not recommend integration where partners are connecting directly to DM. There is no Cisco Unified Computing System Manager because it is not applicable for C-series servers. As a result, you must plan to use Cisco Unified Operations Manager, Cisco Unified Service Manager, and Cisco vcenter directly. If you determine that this functionality is required, consider moving to a Small PoD implementation where Prime Central for HCS is available. Note Be aware that a dedicated server is where one C-series server contains one customer but may have different type of applications for that customer. For details on the Micro Node deployment model see the System Architecture chapter in the Solution Reference Network Design Guide for Cisco Hosted Collaboration Solution 9.2(1) SU1 OL

10 for Micro Node 10 OL