Kontraktbilag 20 - Cisco Health Tjek

Transcription

1 Udbud nr. 2017/S EU-udbud af Cisco UCC i Region Syddanmark Kontraktbilag 20 - Cisco Health Tjek Side 1/10

2 Indholdsfortegnelse OVERSIGT OVER FINDINGS INTRODUKTION HIGH LEVEL FINDINGS 5 OF MEDIUM LEVEL FINDINGS 1-5 OF MEDIUM LEVEL FINDINGS 6-11 OF LOW LEVEL FINDINGS 1-7 OF LOW LEVEL FINDINGS 8-12 OF LOW LEVEL FINDINGS OF LOW LEVEL FINDINGS OF Side 2/10

3 Oversigt over findings i relation til Cisco Health Check af uc&c produktionssystem 1. Introduktion Region Syddanmark har med hjælp fra Cisco Advanced Services gennemført et health check af det samlede platformskompleks bortset fra WebEx og Telepsykiatriløsningen (borgerløsningen). Der er identificeret 40 forhold, som fordeler sig på: 5 high level, 11 medium level og 24 low level Alle er medtaget se nedenfor Venligst bemærk at de findings i Cisco Health tjek, som er vurderet relevante for afklaring i transitionsfasen, er markeret særskilt med teksten NEEDS FIXING. Øvrige findings (med tekster som fx: KNOWN ISSUE, DELIBERATE CHOICE etc.) kan afklares efterfølgende - når Kunden kontraktmæssigt er i almindelig drift - og det vil ske via ændringsanmodning. Side 3/10

4 2. High level findings 5 of 5 During the health check and discussions we did not come across a test If possible build system for environment, test environment considering the nature with mirrored of the system, we configuration and 1 No test system would highly components High recommend that (hardware, software). consideration is given Every change could to maintaining test be tested in LAB systems before introducing in production system No need to fix. Not relevant for sla no chapter reference 6 CUCM call routing Limited number of ISDN b channels for Hospital PSTN connections in case of failover" Consider going to SIP instead of ISDN on local PSTN gateways to increase number of logical channels High No need to fix. Not relevant for sla chapter UCCX 10-video CUCM Pub CPU utilization VCS Expressway unauthorized registration SYSLOG check - CPU is over utilized on CUCM Chapter CPU is over utilized on UCCX Chapter There s no restriction for authorized clients registration on VCS Expressway. Chapter Raise a TAC case for detailed troubleshooting and High root cause of high CPU utilization. Consider a centralized wallboard server that asks UCCX for High stats. Additionally raise a TAC case to check database issues. Implement configuration which would require authorization for registration on VCS Expressway High Side 4/10

5 3. level findings 1-5 of 11 2 CUCM Cluster upgrade EoX dates to be reached soon on existing CUCM cluster Plan CUCM cluster upgrade to newer version Chapters 4.1.6, CUCM One node is over configured with endpoints and some Call Manager Groups will not be capable to register all endpoints in case of failure Analyse and adjust some Call Manager groups to be capable of phone registration during failover. Chapter UCCX Too many CTI ports configured Chapter Analyse the number of unused CTI ports. Only 400 simultaneous calls can be queued at the same time 12 UCCX EoX dates to be reached soon on existing UCCX cluster Plan UCCX cluster upgrade to newer version Chapters 4.3.4, CUC Cluster upgrade EoX dates to be reached soon on existing CUC cluster Plan CUC cluster upgrade to newer version Chapter 4.4.6, Side 5/10

6 4. level findings 6-11 of IM&P Cluster upgrade End-of-Sale and End-of- Support dates haven t been announced. System upgrade is advised to be compliant with other voice components Plan IM&P cluster upgrade to newer version 23 Jabber Guest 28 PSTN gateways IOS upgrade Chapter 4.5.6, No optimal call routing configured on Expressway-C Chapter EoX dates to be reached soon on existing system Change call routing from jabber guest no to pass through public network Plan IOS upgrade to newer version fixed 2-video 3-video TelePresence Conductor with CUCM integration VCS Control Traversal Zone to VCS Expressway Chapter TelePresence Conductor is integrated with CUCM cluster using physical IP addresses not in redundant way Chapter DNS records for VCS Expressway cluster nodes configured in a way which can affect its Register Conductor on CUCM cluster with virtual IP addresses. Configure on CUCM Media Resource Groups and Media Resource Group Lists Change DNS records in order to have each FQDN resolvable to a single IP address Chapter video TMSPE to VCS replication warning There s a system warning in TMS and VCS regarding potential issue with phone books replication. Further investigation with TAC is needed. Side 6/10

7 5. level findings 1-7 of 24 3 Licensing 4 CUCM Services 7,8 CUCM call Routing Some users are not associated with devices. Unnecessary licenses are utilized. Chapter Some unnecessary services are running on CUCM Chapter CTI ports should not be used for call forward Chapter Associate devices with end users in CUCM to reduce licence utilization. Some services running on the cluster are potentially not required. Should be verified with the Analyse and reconfigure method of call transferring to mobile / Dects. Different trunk types interconnect CUCM and For a consistency SME purpose reconfigure trunk to SME with only one protocol Chapter SME Services Some unnecessary services are running on SME Some services running on the cluster are potential not required. Should be verified with the partner. Chapter IM&P High availability One node in sub cluster is in backup mode Manually fall back primary node to become active Chapter IM&P integration with Exchange SSL Connection shows missing certificates error Check the certificate, upload valid one if needed. fix is pending Chapter Side 7/10

8 6. level findings 8-12 of Jabber for UC 19, 20 21, 22, Unused voic UC Change the protocol Service configured for from HTTP to using http on port 443 HTTPS on s199dc1- cucpub60.rsyd.net Chapter UC Service. No is deployed on Expressway-C and Chapter , Single NIC with NAT enabled on Expressway-Change deployment E model to have dual NIC Chapter Deploy redundant Expresway-C and Expresway-E server Deliberate choice to be Fixed later. Target Jabber Guest Mobile Remote Access H323 protocol is enabled Chapter , Disable H323 while it is not deployed for MRA 2 nd NTP server is not accessible Chapter Check the accessibility of redundant NTP server to properly sync time in case primary NTP fails. Side 8/10

9 7. level findings of 24 24,25,26,27 Jabber Guest Single NIC with NAT enabled on Expressway-Change deployment E model to have dual NIC Chapter No is deployed on Expressway-C and Chapters , H323 protocol is enabled Chapters , nd NTP server is not accessible Chapter Deploy redundant Expressway-C and Expressway-E server Disable H323 while it is not deployed for Jabber guests Check the accessibility of redundant NTP server to properly sync time in case primary NTP fails. Deliberate choice to be fixed later. Target jabber expway 29 PRI status Some PRIs are not operational Contact with Telco provider to troubleshoot connectivity known issue Chapter PSTN gateways MGCP Additional SME call processing node is missing as redundant host in MGCP configuration Chapter Configure 2 nd SME as redundant host. In case one node becomes unavailable, gateway will register to redundant node. Side 9/10

10 8. level findings of 24 1-Video MSE 8710 cascading MSE 8710 cascading is Configure Tele used instead of Presence Server clustering non optimal cascading to optimize the Chapter resource allocation 4-Video TMS TMS is deployed with no Enable and deploy second TMS server. known issue 5-Video TMS with CUCM integration There s only one CUCM cluster node added in to TMS. Add in to TMS additional CUCM cluster nodes 6-Video TMS licenses Almost all TMS system licenses are used. Additional licenses might be needed, alternative option is to purge old devices (see the next item) known issue 7-Video TMS database clean-up needed Many endpoints added in to TMS are not accessible any more. Purge old devices which do not exist any more 8-Video TMS endpoints configuration clean-up needed There re some endpoints added in to TMS with a wrong username or password Proper credentials to be configuration on TMS Side 10/10