分享
分享赚钱 收藏 举报 版权申诉 / 13

类型排除故障新的plm的新增内容对hcm-f.pdf

  • 上传人:kuailexingkong
  • 文档编号:1607589
  • 上传时间:2018-08-10
  • 格式:PDF
  • 页数:13
  • 大小:329.91KB
  • 配套讲稿:

    如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。

    特殊限制:

    部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。

    关 键  词:
    排除故障新的plm的新增内容对hcm-f.pdf
    资源描述:

    1、排除故障新的PLM的新增内容对HCM-F 目录简介先决条件要求使用的组件问题:HCM-F管理员不是能添加每新的PLM2实例解决方案1。解决方案2。解决方案3。解决方案4。解决方案5。相关信息简介本文描述如何排除故障托管的许可证管理器(HLM)和头等许可证管理器(PLM),当一新的PLM添加了。在您开TAC案例前,请执行此清单。先决条件要求Cisco 建议您了解以下主题:思科托管协作解决方案(HCS)a71思科托管协作斡旋功能(HCM-F)a71ELM/PLM的许可证安装a71使用的组件本文档中的信息基于以下软件和硬件版本:HCM-F 10.6.2a71PLM 10.5.2a71本文档中的信息都

    2、是基于特定实验室环境中的设备编写的。本文档中使用的所有设备最初均采用原始(默认)配置。如果您使用的是真实网络,请确保您已经了解所有命令的潜在影响。问题:HCM-F管理员不是能添加每新的PLM2实例这是被看到的错误消息。 当几个情况可能导致同一个GUI错误,为了排除故障此问题, HLM被选派的日志要求。1. 登录HCM-F。CLI启用日志成水平并且收集日志。2. 运行集trace tracelevel命令。3. 输入tracelevel (使用CLI显示在orderto查找允许的tracelevels的tracelevels)。4. 输入servicename : 思科HCS许可证管理器服务。5

    3、. 再生产问题并且收集与此file命令的日志获得activelog /hcs/HLM/ *。解决方案1。HLM日志显示HLM不能创建对由于的PLM的一代表状态转移(其余)连接连接超时。| 2016-09-02 04:52:55.025 | 63406 | SdlSig | CreateELMRequest | null0 | HLM(HLMCORE) |SDRUI(NBI-HLM-v90- LIB0) | null2016-09-02 16:52:55,025 INFO 63406 HLMCoreAgent:null0_CreateELMRequest is fired.2016-09-02

    4、16:52:55,025 INFO 63406 HLMCoreAgent:null0_CreateELMRequest recieved2016-09-02 16:52:55,025 INFO 63406 HLMCoreAgent:elmName PLM22016-09-02 16:52:55,025 INFO 63406 HLMCoreAgent:elmHost PLM22016-09-02 16:52:55,025 INFO 63406 HLMCoreAgent:elmUser administrator2016-09-02 16:52:55,025 INFO 63406 HLMCoreA

    5、gent:elmPass *2016-09-02 16:52:55,025 INFO 63406 HLMCoreAgent:deploymentMode HCS2016-09-02 16:52:55,025 INFO 63406 HLMCoreAgent:null0_CreateELMRequest opening RESTconnection to supplied LM2016-09-02 16:52:55,025 INFO 63406 ELMApi: init, connecting to PLM22016-09-02 16:52:55,025 DEBUG 63406 Got the s

    6、slCtx2016-09-02 16:52:55,025 INFO 63406 Initialized the context2016-09-02 16:52:55,096 INFO 63406 ELMApi: initialized with connection timeout, connected toPLM22016-09-02 16:52:55,096 INFO 63406 HLMCoreAgent:null0_CreateELMRequest validating connectionto LM2016-09-02 16:52:55,096 DEBUG 63406 ELMApi:

    7、validateConnection Called2016-09-02 16:52:55,097 ERROR 63406 ELMApi: ClientHanglerException caught validatingconnection, throwing C onnectException2016-09-02 16:52:55,097 ERROR 63406 HLMCoreAgent:CreateELMRequest Exception:.UnknownHostException: PLM2-2016-09-02 16:52:55,100 DEBUG 63406 Agent: Sent m

    8、essage to SDRUI(NBI-HLM-v90-LIB0)2016-09-02 16:52:55,100 DEBUG 63406 HLMCoreAgent:CreateELMResponse message was sent.2016-09-02 16:52:55,100 ERROR 63406 Sdl.5 | 2016-09-02 04:52:55.100 | 63406 | SdlExcept | CreateELMRequest | null0 | HLM(HLMCORE) |SDRUI(NBI-HLM-v 90-LIB0) | Error in fire: .UnknownHo

    9、stException:PLM22016-09-02 16:52:55,101 ERROR 63406 Agent caught exception while processing message typeCreateELMRequestcom.sun.jersey.api.client.ClientHandlerException: .UnknownHostException: PLM2atcom.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.j av

    10、a:151)添加直接和反向查找在域名服务器里(DNS)的HCS管理如这些镜像所显示,并且验证所有连通性问题。验证运行命令。admin:show network eth0Ethernet 0DHCP : disabled Status : upIP Address : 10.48.50.70 IP Mask : 255.255.255.128Link Detected: yes Mode : Auto disabled, Full, 1000 Mbits/sDuplicate IP : noDNSPrimary : 10.48.55.76 Secondary : Not ConfiguredOp

    11、tions : timeout:5 attempts:2Domain : Gateway : 10.48.50.1 on Ethernet 0admin:utils network ping plm2PING (10.48.50.72) 56(84) bytes of data.64 bytes from (10.48.50.72): icmp_seq=1 ttl=64 time=0.484 ms64 bytes from (10.48.50.72): icmp_seq=2 ttl=64 time=0.493 ms64 bytes from (10.48.50.72): icmp_se

    12、q=3 ttl=64 time=0.441 ms64 bytes from (10.48.50.72): icmp_seq=4 ttl=64 time=0.590 ms- ping statistics -4 packets transmitted, 4 received, 0% packet loss, time 3021msrtt min/avg/max/mdev = 0.441/0.502/0.590/0.054 ms解决方案2。HLM日志显示HLM能创建与PLM实例,但是PLM回复的其余连接返回与没找到的“404错误消息”。2016-09-02 17:01:08,561 INFO

    13、63414 ELMApi: initialized with connection timeout, connected to10.48.55.292016-09-02 17:01:08,561 INFO 63414 HLMCoreAgent:null0_CreateELMRequest validating connectionto LM2016-09-02 17:01:08,561 DEBUG 63414 ELMApi: validateConnection Called2016-09-02 17:01:08,614 ERROR 63414 HLMCoreAgent:CreateELMRe

    14、quest Exception: GEThttps:/10.48.55.29/elm-resources returned a response status of 404 Not Found2016-09-02 17:01:08,616 DEBUG 63414 Agent: sending to SDRUI-CreateELMResponseHLMHLMCORESDRUINBI-HLM-v90-LIB0b0a354ec-6249-4cf6-ac7d-f73bac6918d4trueGET https:/10.48.55.29/elm-resources returned a response

    15、 status of 404 NotFoundcom.cisco.hcs.HLM.core.HLMCoreAgent$null0_CreateELMRequest.fire(HLMCoreAgent.java:363)com.cisco.hcs.hcsagent.agent.AgentFSM.fireTransition(AgentFSM.java:554)com.cisco.hcs.hcsagent.agent.AgentFSM.fire(AgentFSM.java:445)com.cisco.hcs.hcsagent.agent.Agent.process(Agent.java:324)c

    16、om.cisco.hcs.hcsagent.agent.AgentTask.run(AgentTask.java:75)java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)java.util.concurrent.FutureTask.run(FutureTask.java:262)java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)java.util.concurrent.ThreadPoolExe

    17、cutor$Worker.run(ThreadPoolExecutor.java:615)java.lang.Thread.run(Thread.java:745)false0-2016-09-02 17:01:08,618 DEBUG 63414 Agent: Sent message to SDRUI(NBI-HLM-v90-LIB0)2016-09-02 17:01:08,618 DEBUG 63414 HLMCoreAgent:CreateELMResponse message was sent.2016-09-02 17:01:11,625 INFO 63414 AgentFSM:c

    18、urrentState changed from null0 to null0The PLM API services must be activeted in order to fix the issue.Run the following commands from PLM CLI.admin:utils service activate Cisco Prime LM Resource APIService Manager is runningCisco Prime LM Resource APISTARTEDadmin:utils service activate Cisco Prime

    19、 LM Resource Legacy APIService Manager is runningCisco Prime LM Resource Legacy APISTARTED验证从PLM CLI运行命令。admin utils service listCisco Prime LM AdminSTARTEDCisco Prime LM DBSTARTEDCisco Prime LM Resource APISTARTEDCisco Prime LM Resource Legacy APISTARTED解决方案3。HLM日志显示PLM在演示模式运行。11 | 2016-09-02 05:21

    20、:07.615 | 63406 | SdlSig | CreateELMRequest | null0 | HLM(HLMCORE) |SDRUI(NBI-HLM-v90-LIB0) | null2016-09-02 17:21:07,615 INFO 63406 HLMCoreAgent:null0_CreateELMRequest is fired.2016-09-02 17:21:07,615 INFO 63406 HLMCoreAgent:null0_CreateELMRequest recieved2016-09-02 17:21:07,615 INFO 63406 HLMCoreA

    21、gent:elmName PLM22016-09-02 17:21:07,615 INFO 63406 HLMCoreAgent:elmHost 10.48.55.292016-09-02 17:21:07,615 INFO 63406 HLMCoreAgent:elmUser administrator2016-09-02 17:21:07,615 INFO 63406 HLMCoreAgent:elmPass *2016-09-02 17:21:07,615 INFO 63406 HLMCoreAgent:deploymentMode HCS2016-09-02 17:21:07,615

    22、INFO 63406 HLMCoreAgent:null0_CreateELMRequest opening RESTconnection to supplied LM2016-09-02 17:21:07,615 INFO 63406 ELMApi: init, connecting to 10.48.55.292016-09-02 17:21:07,615 DEBUG 63406 Got the sslCtx2016-09-02 17:21:07,615 INFO 63406 Initialized the context2016-09-02 17:21:07,687 INFO 63406

    23、 ELMApi: initialized with connection timeout, connected to10.48.55.292016-09-02 17:21:07,687 INFO 63406 HLMCoreAgent:null0_CreateELMRequest validating connectionto LM2016-09-02 17:21:07,687 DEBUG 63406 ELMApi: validateConnection Called2016-09-02 17:21:07,795 DEBUG 63406 ELMApi: connection Validated2

    24、016-09-02 17:21:07,795 DEBUG 63406 ELMApi: getELMReg Called2016-09-02 17:21:07,846 INFO 63406 HLMCoreAgent:Found LM to be in Demo Mode2016-09-02 17:21:07,846 DEBUG 63406 HLMCoreAgent: CreateELMRequest closing the connection2016-09-02 17:21:07,847 DEBUG 63406 Agent: sending to SDRUI-CreateELMResponse

    25、HLMHLMCORESDRUINBI-HLM-v90-LIB0ae3b7f12-d5cb-4db4-bc37-291833d00f83trueELM is in demo license.CreateELMResponseHLMHLMCORESDRUINBI-HLM-v90-LIB0ab8cbfc5-cbe5-4c3f-8c33-324517d69d7dtrueELM is in demo license.添加HCS许可证到PLM并且再尝试添加PLM。验证登陆对PLM用户界面并且点击。在您添加HCS许可证后,如镜像所显示, PLM出现有效registritation ID :解决方案4。HLM

    26、能与与401消息的PLM,但是PLM回复联系。12 | 2016-09-02 05:22:51.594 | 63414 | SdlSig | CreateELMRequest | null0 | HLM(HLMCORE) |SDRUI(NBI-HLM-v90-LIB0) | null2016-09-02 17:22:51,594 INFO 63414 HLMCoreAgent:null0_CreateELMRequest is fired.2016-09-02 17:22:51,594 INFO 63414 HLMCoreAgent:null0_CreateELMRequest recieve

    27、d2016-09-02 17:22:51,595 INFO 63414 HLMCoreAgent:elmName PLM22016-09-02 17:22:51,595 INFO 63414 HLMCoreAgent:elmHost 10.48.55.292016-09-02 17:22:51,595 INFO 63414 HLMCoreAgent:elmUser administrator2016-09-02 17:22:51,595 INFO 63414 HLMCoreAgent:elmPass *2016-09-02 17:22:51,595 INFO 63414 HLMCoreAgen

    28、t:deploymentMode HCS2016-09-02 17:22:51,595 INFO 63414 HLMCoreAgent:null0_CreateELMRequest opening RESTconnection to supplied LM2016-09-02 17:22:51,595 INFO 63414 ELMApi: init, connecting to 10.48.55.292016-09-02 17:22:51,595 DEBUG 63414 Got the sslCtx2016-09-02 17:22:51,595 INFO 63414 Initialized t

    29、he context2016-09-02 17:22:51,673 INFO 63414 ELMApi: initialized with connection timeout, connected to10.48.55.292016-09-02 17:22:51,673 INFO 63414 HLMCoreAgent:null0_CreateELMRequest validating connectionto LM2016-09-02 17:22:51,673 DEBUG 63414 ELMApi: validateConnection Called2016-09-02 17:22:53,5

    30、46 ERROR 63414 HLMCoreAgent:CreateELMRequest Exception: GEThttps:/10.48.55.29/elm-resources returned a response status of 401 Unauthorized2016-09-02 17:22:53,548 DEBUG 63414 Agent: sending to SDRUI-CreateELMResponseHLMHLMCORESDRUINBI-HLM-v90-LIB006e919ba-1c30-47bb-b72d-a4a0a1ca049ctrueGET https:/10.

    31、48.55.29/elm-resources returned a response status of 401Unauthorizedcom.cisco.hcs.HLM.core.HLMCoreAgent$null0_CreateELMRequest.fire(HLMCoreAgent.java:363)添加PLM OS Admin用户ID和密码。解决方案5。HLM能与PLM联系,然而PLM回复返回与一个不兼容版本。2016-09-05 11:53:19,131 INFO 63394 HLMCoreAgent:null0_CreateELMRequest is fired.2016-09-0

    32、5 11:53:19,131 INFO 63394 HLMCoreAgent:null0_CreateELMRequest recieved2016-09-05 11:53:19,132 INFO 63394 HLMCoreAgent:elmName PLM112016-09-05 11:53:19,132 INFO 63394 HLMCoreAgent:elmHost 10.48.53.1202016-09-05 11:53:19,132 INFO 63394 HLMCoreAgent:elmUser admin2016-09-05 11:53:19,132 INFO 63394 HLMCo

    33、reAgent:elmPass *2016-09-05 11:53:19,132 INFO 63394 HLMCoreAgent:deploymentMode HCS2016-09-05 11:53:19,132 INFO 63394 HLMCoreAgent:null0_CreateELMRequest opening RESTconnection to supplied LM2016-09-05 11:53:19,132 INFO 63394 ELMApi: init, connecting to 10.48.53.1202016-09-05 11:53:19,132 DEBUG 6339

    34、4 Got the sslCtx2016-09-05 11:53:19,132 INFO 63394 Initialized the context2016-09-05 11:53:19,206 INFO 63394 ELMApi: initialized with connection timeout, connected to10.48.53.1202016-09-05 11:53:19,206 INFO 63394 HLMCoreAgent:null0_CreateELMRequest validating connectionto LM2016-09-05 11:53:19,206 D

    35、EBUG 63394 ELMApi: validateConnection Called2016-09-05 11:53:19,457 DEBUG 63394 ELMApi: connection Validated2016-09-05 11:53:19,457 DEBUG 63394 ELMApi: getELMReg Called2016-09-05 11:53:19,560 DEBUG 63394 ELMApi: getELMVer Called2016-09-05 11:53:19,667 DEBUG 63394 HLMCoreAgent:null0_createELMRequest

    36、LM PLM11 version is11.0.1.10000-22016-09-05 11:53:19,667 DEBUG 63394 hlmSDRUtil.createELM2016-09-05 11:53:19,669 DEBUG 63394 hlmSDRUtil.getHCMFDeploymentMode2016-09-05 11:53:19,669 DEBUG 63394 hlmSDRUtil.beginTransaction2016-09-05 11:53:19,670 DEBUG 63394 hlmSDRUtilcommitTransaction2016-09-05 11:53:

    37、19,671 DEBUG 63394 hlmSDRUtil.beginTransaction2016-09-05 11:53:19,672 INFO 63394 LM version is 11.0.1.10000-22016-09-05 11:53:19,673 ERROR 63394 hlmSDRUtil.createELM: SDR exception(SDRSyncSession): null2016-09-05 11:53:19,673 DEBUG 63394 hlmSDRUtil.rollbackTransaction2016-09-05 11:53:19,673 ERROR 63394 HLMCoreAgent:CreateELMRequest Exception: AttributeTypeELMVersion is required.保证补充说的PLM版本由HCM-F suported和是指HCS兼容性矩阵。相关信息http:/ - Cisco Systemsa71

    展开阅读全文
    提示  道客多多所有资源均是用户自行上传分享,仅供网友学习交流,未经上传用户书面授权,请勿作他用。
    关于本文
    本文标题:排除故障新的plm的新增内容对hcm-f.pdf
    链接地址:https://www.docduoduo.com/p-1607589.html
    关于我们 - 网站声明 - 网站地图 - 资源地图 - 友情链接 - 网站客服 - 联系我们

    道客多多用户QQ群:832276834  微博官方号:道客多多官方   知乎号:道客多多

    Copyright© 2025 道客多多 docduoduo.com 网站版权所有世界地图

    经营许可证编号:粤ICP备2021046453号    营业执照商标

    1.png 2.png 3.png 4.png 5.png 6.png 7.png 8.png 9.png 10.png



    收起
    展开