Solução de problemas ao adicionar uma nova instância de produto de aplicativo UC no PLM via HCM-F

Introduction

Este documento descreve as etapas gerais de solução de problemas do Hosted License Manager (HLM) e do Prime License Manager (PLM) ao adicionar uma nova instância de produto do Unified Application no PLM via HCM-F. Além disso, execute a lista de verificação antes de abrir um caso no TAC.

Prerequisites

Requirements

A Cisco recomenda que você tenha conhecimento destes tópicos:

• Cisco Hosted Collaboration Solution (HCS)
• Cisco Hosted Collaboration Mediation Function (HCM-F)
• Cisco Prime License Manager (PLM)

Componentes Utilizados

As informações neste documento são baseadas nestas versões de software e hardware:

• HCM-F 10.6.2
• PLM 10.5.2

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Problema: O administrador do HCM-F não pode atribuir o cluster UC à instância do PLM

O trabalho HCM-F falha com o erro mostrado na imagem:

Para solucionar esse problema, os registros detalhados de HLM são necessários, pois várias condições podem levar ao mesmo erro de GUI.

Faça login no HCM-F, a CLI ativa o nível de logs e coleta os logs.

Execute o comando:

set trace tracelevel

Digite o tracelevel(use CLI "show traconze" para encontrar os níveis de rastreamento permitidos) :: Detalhado

Insira o nome do serviço :: Serviço do Cisco HCS License Manager

Reproduza o problema e colete os registros.

file get ativelog /hcs/HLM/*

Solução 1

Adicione o endereço IP do provedor de serviços no Editor do aplicativo de cluster. O HCM-F não pode se conectar ao aplicativo UC porque o provedor de serviços IP está ausente.

2016-09-21 18:25:21,659 INFO  [264674] UCAppDeploymentModeConnection: Opening secure connection to: https://null:8443/platform-services/services/DeploymentModeService?wsdl

2016-09-21 18:25:21,659 INFO  [264674] UCAppDeploymentModeConnectionPort successfully opened

2016-09-21 18:25:21,688 INFO  [264674] UCAppDeploymentModeConnection: Setting userName for SOAP connection to: ccmadmin

2016-09-21 18:25:21,688 INFO  [264674] UCAppDeploymentModeConnection: Accepting Certificate from UC Application

2016-09-21 18:25:21,688 INFO  [264674] UCAppDeploymentModeConnection.getDeploymentMode Called

2016-09-21 18:25:21,695 ERROR [264674] UCAppAPI.getDeploymentMode() CaughtException: Error writing to XMLStreamWriter.

2016-09-21 18:25:21,695 ERROR [264674] HLMClusterLicenseAgent: .null0_AssignClusterToELMRequest  Error writing to XMLStreamWriter.

2016-09-21 18:25:21,696 DEBUG [264674] hlmSDRUtil.updateJob

2016-09-21 18:25:21,750 DEBUG [264674] hlmSDRUtil.beginTransaction

 

Verificar

Para verificar, navegue para Gerenciamento de aplicativos > Aplicativo de cluster

Solução 2

Ative a conectividade IP entre o HCM-F e o aplicativo UC na porta 8443.

A configuração do HCM-F está correta, mas o módulo HLM não pode abrir uma conexão tcp para o aplicativo UC. Consulte a seção Verificar como solucionar mais esse problema

2016-09-21 18:34:33,745 INFO  [264677] UCAppDeploymentModeConnection: Opening secure connection to: https://10.48.50.72:8443/platform-services/services/DeploymentModeService?wsdl

2016-09-21 18:34:33,746 INFO  [264677] UCAppDeploymentModeConnectionPort successfully opened

2016-09-21 18:34:33,764 INFO  [264677] UCAppDeploymentModeConnection: Setting userName for SOAP connection to: ccmadmin

2016-09-21 18:34:33,764 INFO  [264677] UCAppDeploymentModeConnection: Accepting Certificate from UC Application

2016-09-21 18:34:33,764 INFO  [264677] UCAppDeploymentModeConnection.getDeploymentMode Called

Failed to connect :

2016-09-21 18:35:09,801 ERROR [264677] UCAppAPI.getDeploymentMode() CaughtException: Error writing to XMLStreamWriter.

2016-09-21 18:35:09,801 ERROR [264677] HLMClusterLicenseAgent: .null0_AssignClusterToELMRequest  Error writing to XMLStreamWriter.

2016-09-21 18:35:09,801 DEBUG [264677] hlmSDRUtil.updateJob

2016-09-21 18:35:09,856 DEBUG [264677] hlmSDRUtil.beginTransaction

2016-09-21 18:35:09,859 DEBUG [264677] hlmSDRUtilcommitTransaction

2016-09-21 18:35:09,990 INFO  [264677] AgentFSM::currentState changed from null0 to stopped

2016-09-21 18:35:09,990 INFO  [264677] Agent route no longer needed...moving it to stopped routes

2016-09-21 18:35:09,990 INFO  [264677] Route removed from context >HLM(be75ce6c-f4ca-464e-aa0f-8204f6cb1fa3)<

 Verificar

• Verifique se o aplicativo UC está ativo e em execução.

• Verifique a conectividade entre o aplicativo UC e HCM-F.

admin:utils network ping XXX.YYY.WWW.ZZZ

• Verifique se a porta 8443 não está bloqueada pelo firewall. Colete a captura de pacotes e verifique se o aperto manual do TCP foi estabelecido com êxito.
  

admin:utils network capture eth0 file filename count 10000 size all port 8443 host ip xxx.yyy.www.zzz

onde xxx.yyy.www.zzz é o espaço do serviço de aplicativos UC

• Verifique se o link abaixo está acessível.
  

https://UC_APP_IP_ADDRRESS:8443/platform-services/services/DeploymentModeService?wsdl

Solução 3

• Digite novamente a senha do aplicativo UC da plataforma para corresponder à do aplicativo UC, pois o HLM não pode enviar a mensagem.
  
  
• Iniciar o serviço da Web Administrador da plataforma no aplicativo UC

2016-10-06 16:24:49,592 INFO  [252833] UCAppDeploymentModeConnection: Opening secure connection to: https://10.48.50.14:8443/platform-services/services/DeploymentModeService?wsdl

2016-10-06 16:24:49,592 INFO  [252833] UCAppDeploymentModeConnectionPort successfully opened

2016-10-06 16:24:49,616 INFO  [252833] UCAppDeploymentModeConnection: Setting userName for SOAP connection to: ccmadmin

2016-10-06 16:24:49,616 INFO  [252833] UCAppDeploymentModeConnection: Accepting Certificate from UC Application

2016-10-06 16:24:49,616 INFO  [252833] UCAppDeploymentModeConnection.getDeploymentMode Called

2016-10-06 16:24:51,877 ERROR [252833] UCAppAPI.getDeploymentMode() CaughtException: Could not send Message.

2016-10-06 16:24:51,878 ERROR [252833] HLMClusterLicenseAgent: .null0_AssignClusterToELMRequest  Could not send Message.

2016-10-06 16:24:51,878 DEBUG [252833] hlmSDRUtil.updateJob

2016-10-06 16:24:51,939 DEBUG [252833] hlmSDRUtil.beginTransaction

2016-10-06 16:24:51,942 DEBUG [252833] hlmSDRUtilcommitTransaction

2016-10-06 16:24:52,054 INFO  [252833] AgentFSM::currentState changed from null0 to stopped

2016-10-06 16:24:52,054 INFO  [252833] Agent route no longer needed...moving it to stopped routes

2016-10-06 16:24:52,054 INFO  [252833] Route removed from context >HLM(ad495160-864d-4b74-8aec-cc708036b5e0)<

2016-10-06 16:24:52,054 DEBUG [252833]
 

Verificar

• Verifique se o serviço Web de administração de plataforma está em execução nos aplicativos UC

Navegue até Cisco Unified Serviceability > Platform Service > Platform Administrative Web Service

• Verifique as respostas do serviço Web de administração de plataforma ao acessar o arquivo wsdl

https://UC_APP_IP_ADDRRESS:8443/platform-services/services/DeploymentModeService?wsdl

Solução 4

Entre em contato com o Cisco TAC para alterar novamente o modo de implantação do PLM para HCS

 

2016-10-07 11:37:55,581 INFO  [238120] UCAppDeploymentModeConnection: Opening secure connection to: https://10.48.52.10:8443/platform-services/services/DeploymentModeService?wsdl

2016-10-07 11:37:55,581 INFO  [238120] UCAppDeploymentModeConnectionPort successfully opened

2016-10-07 11:37:55,608 INFO  [238120] UCAppDeploymentModeConnection: Setting userName for SOAP connection to: ccmadmin

2016-10-07 11:37:55,608 INFO  [238120] UCAppDeploymentModeConnection: Accepting Certificate from UC Application

2016-10-07 11:37:55,608 INFO  [238120] UCAppDeploymentModeConnection.getDeploymentMode Called

2016-10-07 11:37:55,980 DEBUG [238120] UCAppDeploymentModeConnection.getDeploymentMode Response Recieved

2016-10-07 11:37:55,980 INFO  [238120] UCAppDeploymentModeConnection.getDeploymentMode Completed returning value: Enterprise

2016-10-07 11:37:55,980 INFO  [238120] HLMClusterLicenseAgent: .null0_AssignClusterToELMRequest  Found current UC app deployment mode to be: Enterprise

2016-10-07 11:37:55,980 INFO  [238120] HLMClusterLicenseAgent: .null0_AssignClusterToELMRequest  Found current Global deployment mode to be: HCS

2016-10-07 11:37:55,980 INFO  [238120] HLMClusterLicenseAgent: .null0_AssignClusterToELMRequest  Setting the UC app deployment mode to be: HCS

2016-10-07 11:37:55,981 INFO  [238120] UCAppDeploymentModeConnection: Opening secure connection to: https://10.48.52.10:8443/platform-services/services/DeploymentModeService?wsdl

2016-10-07 11:37:55,981 INFO  [238120] UCAppDeploymentModeConnectionPort successfully opened

2016-10-07 11:37:55,993 INFO  [238120] UCAppDeploymentModeConnection: Setting userName for SOAP connection to: ccmadmin

2016-10-07 11:37:55,993 INFO  [238120] UCAppDeploymentModeConnection: Accepting Certificate from UC Application

2016-10-07 11:37:55,993 INFO  [238120] UCAppDeploymentModeConnection.setDeploymentMode Called

2016-10-07 11:37:56,183 DEBUG [238120] UCAppDeploymentModeConnection.setDeploymentMode Response Recieved

2016-10-07 11:37:56,189 INFO  [238120] UCAppRestartSystemConnection: Opening secure connection to: https://10.48.52.10:8443/platform-services/services/RestartSystemService?wsdl

2016-10-07 11:37:56,205 INFO  [238120] UCAppRestartSystemConnection: Setting userName for SOAP connection to: ccmadmin

2016-10-07 11:37:56,205 INFO  [238120] UCAppRestartSystemConnection: Accepting Certificate from UC Application

 

2016-10-07 11:54:12,248 INFO  [238120] ELMApi: initialized, connected to plm-hcs10

2016-10-07 11:54:12,248 DEBUG [238120] ELMApi: createCluster called - force registration is enabled.

2016-10-07 11:54:12,248 DEBUG [238120] ELMApi:Creating Cluster with clusterName: test-cluster-Z|HostName: 10.48.52.10|userid: ccmadmin|password: ******|Type: HUCM

2016-10-07 11:54:12,360 DEBUG [238120] ELMApi: createCluster  Response status = 400

2016-10-07 11:54:12,360 ERROR [238120] ELMApi: createCluster completes with an error. LM resp status: 400

2016-10-07 11:54:12,360 ERROR [238120] HLMClusterLicenseAgent:  Failed to assign cluster test-cluster-Z due to an internal error in LM plm-hcs10

2016-10-07 11:54:12,360 DEBUG [238120] hlmSDRUtil.updateJob

2016-10-07 11:54:12,412 DEBUG [238120] hlmSDRUtil.beginTransaction

2016-10-07 11:54:12,415 DEBUG [238120] hlmSDRUtilcommitTransaction

2016-10-07 11:54:12,538 INFO  [238120] AgentFSM::currentState changed from null0 to stopped

2016-10-07 11:54:12,539 INFO  [238120] Agent route no longer needed...moving it to stopped routes

2016-10-07 11:54:12,539 INFO  [238120] Route removed from context >HLM(8032fcf3-9368-4644-a46f-46445247e893)<

2016-10-07 11:54:12,539 DEBUG [238120] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2016-10-07 11:54:12,539 DEBUG [238120]  Agent info : HLM(8032fcf3-9368-4644-a46f-46445247e893): RED

Assign test-cluster-Z to plm-hcs10 is Failed

Verificar

Verifique o modo de implantação do PLM navegando na URL abaixo. ID de usuário e senha da plataforma PLM são necessárias

           https://PLM_IP_Address /elm-resources/

Solução 5

Ative a conectividade IP entre HCM-F e PLM na porta 8443. Dos registros, o HLM não consegue se conectar ao PLM

2016-10-18 12:17:47,119 DEBUG [264677] ELMApi:Creating Cluster with clusterName: cluster delta|HostName: 10.48.55.26|userid: administrator|password: ******|Type: HUCM

2016-10-18 12:17:47,904 DEBUG [43] KeepAliveConsumerProcessor::process -- enter

2016-10-18 12:17:47,905 DEBUG [43] KeepAliveConsumerProcessor::process -- received broadcast message for service sdrcnf

2016-10-18 12:17:47,905 DEBUG [43] noChange -- sdrcnf is Alive

2016-10-18 12:17:47,905 DEBUG [43] KeepAliveMonitor::setExpiresBy:

2016-10-18 12:17:47,905 DEBUG [43]   now:         18/10/2016 12:17:47.905

2016-10-18 12:17:47,905 DEBUG [43]   expected by: 18/10/2016 12:19:47.905

2016-10-18 12:17:47,905 DEBUG [71] KeepAliveConsumerProcessor::process -- enter

2016-10-18 12:17:47,906 DEBUG [71] KeepAliveConsumerProcessor::process -- received broadcast message for service sdrcnf

2016-10-18 12:17:47,906 DEBUG [71] noChange -- sdrcnf is Alive

2016-10-18 12:17:47,906 DEBUG [71] KeepAliveMonitor::setExpiresBy:

2016-10-18 12:17:47,906 DEBUG [71]   now:         18/10/2016 12:17:47.906

2016-10-18 12:17:47,906 DEBUG [71]   expected by: 18/10/2016 12:19:47.906

2016-10-18 12:17:50,188 ERROR [264677] HLMClusterLicenseAgent: .null0_AssignClusterToELMRequest  javax.ws.rs.WebApplicationException: javax.xml.bind.MarshalException

- with linked exception:

[java.net.NoRouteToHostException: No route to host]

2016-10-18 12:17:50,188 DEBUG [264677] hlmSDRUtil.updateJob

2016-10-18 12:17:50,247 DEBUG [264677] hlmSDRUtil.beginTransaction

2016-10-18 12:17:50,249 DEBUG [264677] hlmSDRUtilcommitTransaction

2016-10-18 12:17:50,356 INFO  [264677] AgentFSM::currentState changed from null0 to stopped

2016-10-18 12:17:50,356 INFO  [264677] Agent route no longer needed...moving it to stopped routes

Verificar

 Verificar a conectividade entre PLM e HCM-F

admin:utils network ping XXX.YYY.WWW.ZZZ

Problema: O administrador do HCM-F não pode atribuir o cluster UC à instância do PLM

O trabalho falha com o erro mostrado na imagem

;

Solução

Adicionar credencial de plataforma no HCM-F ou no CUCDM

2016-10-06 16:26:48,508 DEBUG [264674] hlmSDRUtilcommitTransaction

2016-10-06 16:26:48,624 ERROR [264674] HLMClusterLicenseAgent: .null0_AssignClusterToELMRequest  no platform credential is configured for test-cluster-Y

2016-10-06 16:26:48,624 DEBUG [264674] hlmSDRUtil.updateJob

2016-10-06 16:26:48,675 DEBUG [264674] hlmSDRUtil.beginTransaction

2016-10-06 16:26:48,677 DEBUG [264674] hlmSDRUtilcommitTransaction

2016-10-06 16:26:48,798 INFO  [264674] AgentFSM::currentState changed from null0 to stopped

2016-10-06 16:26:48,798 INFO  [264674] Agent route no longer needed...moving it to stopped routes

2016-10-06 16:26:48,798 INFO  [264674] Route removed from context >HLM(1b32a922-3619-44b0-8004-7f6fc930c419)<

2016-10-06 16:26:48,798 DEBUG [264674] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2016-10-06 16:26:48,798 DEBUG [264674]  Agent info : HLM(1b32a922-3619-44b0-8004-7f6fc930c419): RED

Assign test-cluster-Y to plm-hcs10 is Failed

2016-10-06 16:26:48,798 DEBUG [264674]  AgentMessageProcessor::Agent is stopped after process, removed it from persistence store

 

Verificar

Verifique se as credenciais da plataforma estão configuradas no HCM-F

Navegue até Gerenciamento de aplicativos > Aplicativo de cluster > Credencial > Plataforma

or

Navegue até Administração > Credencial Padrão > Plataforma do tipo de aplicativo UC (CUCM/CUCXN)