본 제품에 대한 문서 세트는 편견 없는 언어를 사용하기 위해 노력합니다. 본 설명서 세트의 목적상, 편견 없는 언어는 나이, 장애, 성별, 인종 정체성, 민족 정체성, 성적 지향성, 사회 경제적 지위 및 교차성에 기초한 차별을 의미하지 않는 언어로 정의됩니다. 제품 소프트웨어의 사용자 인터페이스에서 하드코딩된 언어, RFP 설명서에 기초한 언어 또는 참조된 서드파티 제품에서 사용하는 언어로 인해 설명서에 예외가 있을 수 있습니다. 시스코에서 어떤 방식으로 포용적인 언어를 사용하고 있는지 자세히 알아보세요.
Cisco는 전 세계 사용자에게 다양한 언어로 지원 콘텐츠를 제공하기 위해 기계 번역 기술과 수작업 번역을 병행하여 이 문서를 번역했습니다. 아무리 품질이 높은 기계 번역이라도 전문 번역가의 번역 결과물만큼 정확하지는 않습니다. Cisco Systems, Inc.는 이 같은 번역에 대해 어떠한 책임도 지지 않으며 항상 원본 영문 문서(링크 제공됨)를 참조할 것을 권장합니다.
이 문서에서는 새 PLM을 추가할 때 HLM(Hosted License Manager) 및 PLM(Prime License Manager)의 문제를 해결하는 방법에 대해 설명합니다.TAC 케이스를 열기 전에 이 체크리스트를 수행합니다.
다음 주제에 대한 지식을 보유하고 있으면 유용합니다.
이 문서의 정보는 다음 소프트웨어 및 하드웨어 버전을 기반으로 합니다.
이 문서의 정보는 특정 랩 환경의 디바이스를 토대로 작성되었습니다.이 문서에 사용된 모든 디바이스는 초기화된(기본) 컨피그레이션으로 시작되었습니다.현재 네트워크가 작동 중인 경우, 모든 명령어의 잠재적인 영향을 미리 숙지하시기 바랍니다.
표시되는 오류 메시지입니다.
이 문제를 해결하려면 여러 조건이 동일한 GUI 오류를 일으킬 수 있으므로 HLM 상세 로그가 필요합니다.
1. HCM-F에 로그인합니다.CLI는 로그 레벨을 활성화하고 로그를 수집합니다.
2. set trace tracelevel 명령을 실행합니다.
3. tracelevel을 입력합니다(허용되는 트레이스를 찾으려면 CLI show traceleves 사용).
4. 서비스 이름(Cisco HCS License Manager Service)을 입력합니다.
5. 이 명령 파일 get activelog /hcs/HLM/*을 사용하여 문제를 재현하고 로그를 수집합니다.
HLM 로그는 연결 시간 제한으로 인해 HLM이 PLM에 대한 REST(Representational State Transfer) 연결을 만들 수 없음을 보여줍니다.
| 2016-09-02 04:52:55.025 | [63406] | SdlSig | CreateELMRequest | null0 | HLM(HLMCORE) | SDRUI(NBI-HLM-v90- LIB0) | null 2016-09-02 16:52:55,025 INFO [63406] HLMCoreAgent:null0_CreateELMRequest is fired... 2016-09-02 16:52:55,025 INFO [63406] HLMCoreAgent:null0_CreateELMRequest recieved 2016-09-02 16:52:55,025 INFO [63406] HLMCoreAgent:elmName PLM2 2016-09-02 16:52:55,025 INFO [63406] HLMCoreAgent:elmHost PLM2 2016-09-02 16:52:55,025 INFO [63406] HLMCoreAgent:elmUser administrator 2016-09-02 16:52:55,025 INFO [63406] HLMCoreAgent:elmPass ****** 2016-09-02 16:52:55,025 INFO [63406] HLMCoreAgent:deploymentMode HCS 2016-09-02 16:52:55,025 INFO [63406] HLMCoreAgent:null0_CreateELMRequest opening REST connection to supplied LM 2016-09-02 16:52:55,025 INFO [63406] ELMApi: init, connecting to PLM2 2016-09-02 16:52:55,025 DEBUG [63406] Got the sslCtx 2016-09-02 16:52:55,025 INFO [63406] Initialized the context 2016-09-02 16:52:55,096 INFO [63406] ELMApi: initialized with connection timeout, connected to PLM2 2016-09-02 16:52:55,096 INFO [63406] HLMCoreAgent:null0_CreateELMRequest validating connection to LM 2016-09-02 16:52:55,096 DEBUG [63406] ELMApi: validateConnection Called 2016-09-02 16:52:55,097 ERROR [63406] ELMApi: ClientHanglerException caught validating connection, throwing C onnectException 2016-09-02 16:52:55,097 ERROR [63406] HLMCoreAgent:CreateELMRequest Exception: java.net.UnknownHostException: PLM2 --------- 2016-09-02 16:52:55,100 DEBUG [63406] Agent: Sent message 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: java.net.UnknownHostException: PLM2 2016-09-02 16:52:55,101 ERROR [63406] Agent caught exception while processing message type CreateELMRequest com.sun.jersey.api.client.ClientHandlerException: java.net.UnknownHostException: PLM2 at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.j ava:151)
DNS(Domain Name Server)의 HCS 관리에서 직접 및 역방향 조회를 추가하고 이러한 이미지에 표시된 대로 연결 문제를 확인합니다.
다음을 확인합니다.
명령을 실행합니다.
admin:show network eth0 Ethernet 0 DHCP : disabled Status : up IP Address : 10.48.50.70 IP Mask : 255.255.255.128 Link Detected: yes Mode : Auto disabled, Full, 1000 Mbits/s Duplicate IP : no DNS Primary : 10.48.55.76 Secondary : Not Configured Options : timeout:5 attempts:2 Domain : hcslab.com Gateway : 10.48.50.1 on Ethernet 0 admin:utils network ping plm2 PING plm2.hcs10.com (10.48.50.72) 56(84) bytes of data. 64 bytes from plm2.hcs10.com (10.48.50.72): icmp_seq=1 ttl=64 time=0.484 ms 64 bytes from plm2.hcs10.com (10.48.50.72): icmp_seq=2 ttl=64 time=0.493 ms 64 bytes from plm2.hcs10.com (10.48.50.72): icmp_seq=3 ttl=64 time=0.441 ms 64 bytes from plm2.hcs10.com (10.48.50.72): icmp_seq=4 ttl=64 time=0.590 ms --- plm2.hcs10.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3021ms rtt min/avg/max/mdev = 0.441/0.502/0.590/0.054 ms
HLM 로그는 HLM이 PLM 인스턴스와 REST 연결을 생성할 수 있지만 PLM은 "404 Not Found(404 찾을 수 없음)"라는 오류 메시지와 함께 회신을 다시 합니다.
2016-09-02 17:01:08,561 INFO [63414] ELMApi: initialized with connection timeout, connected to 10.48.55.29 2016-09-02 17:01:08,561 INFO [63414] HLMCoreAgent:null0_CreateELMRequest validating connection to LM 2016-09-02 17:01:08,561 DEBUG [63414] ELMApi: validateConnection Called 2016-09-02 17:01:08,614 ERROR [63414] HLMCoreAgent:CreateELMRequest Exception: GET https://10.48.55.29/elm-resources returned a response status of 404 Not Found 2016-09-02 17:01:08,616 DEBUG [63414] Agent: sending to [SDRUI] ------- <com.cisco.hcs.HLM.jms.CreateELMResponse> <messageType>CreateELMResponse</messageType> <source> <serviceName>HLM</serviceName> <instance>HLMCORE</instance> </source> <destination> <serviceName>SDRUI</serviceName> <instance>NBI-HLM-v90-LIB0</instance> </destination> <sessionID>b0a354ec-6249-4cf6-ac7d-f73bac6918d4</sessionID> <fault>true</fault> <exception> <detailMessage>GET https://10.48.55.29/elm-resources returned a response status of 404 Not Found</detailMessage> <stackTrace> <trace>com.cisco.hcs.HLM.core.HLMCoreAgent$null0_CreateELMRequest.fire(HLMCoreAgent.java:363)</trace> <trace>com.cisco.hcs.hcsagent.agent.AgentFSM.fireTransition(AgentFSM.java:554)</trace> <trace>com.cisco.hcs.hcsagent.agent.AgentFSM.fire(AgentFSM.java:445)</trace> <trace>com.cisco.hcs.hcsagent.agent.Agent.process(Agent.java:324)</trace> <trace>com.cisco.hcs.hcsagent.agent.AgentTask.run(AgentTask.java:75)</trace> <trace>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)</trace> <trace>java.util.concurrent.FutureTask.run(FutureTask.java:262)</trace> <trace>java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)</trace> <trace>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)</trace> <trace>java.lang.Thread.run(Thread.java:745)</trace> </stackTrace> <suppressedExceptions class="java.util.Collections$UnmodifiableRandomAccessList" resolves-to="java.util.Collections$UnmodifiableList"> <c class="list"/> <list reference="../c"/> </suppressedExceptions> </exception> <Fork>false</Fork> <requeueCount>0</requeueCount> </com.cisco.hcs.HLM.jms.CreateELMResponse> --------- 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::currentState changed from null0 to null0 The 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 API Service Manager is running Cisco Prime LM Resource API[STARTED] admin:utils service activate Cisco Prime LM Resource Legacy API Service Manager is running Cisco Prime LM Resource Legacy API[STARTED]
다음을 확인합니다.
PLM CLI에서 명령을 실행합니다.
admin utils service list Cisco Prime LM Admin[STARTED] Cisco Prime LM DB[STARTED] Cisco Prime LM Resource API[STARTED] Cisco Prime LM Resource Legacy API[STARTED]
HLM 로그는 PLM이 데모 모드에서 실행됨을 보여줍니다.
11 | 2016-09-02 05:21:07.615 | [63406] | SdlSig | CreateELMRequest | null0 | HLM(HLMCORE) | SDRUI(NBI-HLM-v90-LIB0) | null 2016-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 recieved 2016-09-02 17:21:07,615 INFO [63406] HLMCoreAgent:elmName PLM2 2016-09-02 17:21:07,615 INFO [63406] HLMCoreAgent:elmHost 10.48.55.29 2016-09-02 17:21:07,615 INFO [63406] HLMCoreAgent:elmUser administrator 2016-09-02 17:21:07,615 INFO [63406] HLMCoreAgent:elmPass ****** 2016-09-02 17:21:07,615 INFO [63406] HLMCoreAgent:deploymentMode HCS 2016-09-02 17:21:07,615 INFO [63406] HLMCoreAgent:null0_CreateELMRequest opening REST connection to supplied LM 2016-09-02 17:21:07,615 INFO [63406] ELMApi: init, connecting to 10.48.55.29 2016-09-02 17:21:07,615 DEBUG [63406] Got the sslCtx 2016-09-02 17:21:07,615 INFO [63406] Initialized the context 2016-09-02 17:21:07,687 INFO [63406] ELMApi: initialized with connection timeout, connected to 10.48.55.29 2016-09-02 17:21:07,687 INFO [63406] HLMCoreAgent:null0_CreateELMRequest validating connection to LM 2016-09-02 17:21:07,687 DEBUG [63406] ELMApi: validateConnection Called 2016-09-02 17:21:07,795 DEBUG [63406] ELMApi: connection Validated 2016-09-02 17:21:07,795 DEBUG [63406] ELMApi: getELMReg Called 2016-09-02 17:21:07,846 INFO [63406] HLMCoreAgent:Found LM to be in Demo Mode 2016-09-02 17:21:07,846 DEBUG [63406] HLMCoreAgent: CreateELMRequest closing the connection 2016-09-02 17:21:07,847 DEBUG [63406] Agent: sending to [SDRUI] ------- <com.cisco.hcs.HLM.jms.CreateELMResponse> <messageType>CreateELMResponse</messageType> <source> <serviceName>HLM</serviceName> <instance>HLMCORE</instance> </source> <destination> <serviceName>SDRUI</serviceName> <instance>NBI-HLM-v90-LIB0</instance> </destination> <sessionID>ae3b7f12-d5cb-4db4-bc37-291833d00f83</sessionID> <fault>true</fault> <exception> <detailMessage>ELM is in demo license.</detailMessage> <stackTrace> <com.cisco.hcs.HLM.jms.CreateELMResponse> <messageType>CreateELMResponse</messageType> <source> <serviceName>HLM</serviceName> <instance>HLMCORE</instance> </source> <destination> <serviceName>SDRUI</serviceName> <instance>NBI-HLM-v90-LIB0</instance> </destination> <sessionID>ab8cbfc5-cbe5-4c3f-8c33-324517d69d7d</sessionID> <fault>true</fault> <exception> <detailMessage>ELM is in demo license.</detailMessage> <stackTrace>
PLM에 HCS 라이센스를 추가하고 PLM을 다시 추가하려고 합니다.
다음을 확인합니다.
PLM 사용자 인터페이스에 로그인하고 About(정보)을 클릭합니다.HCS 라이센스를 추가한 후 PLM은 이미지에 표시된 대로 유효한 등록 ID를 표시합니다.
HLM은 PLM에 연결할 수 있지만 PLM은 401 메시지로 회신합니다.
12 | 2016-09-02 05:22:51.594 | [63414] | SdlSig | CreateELMRequest | null0 | HLM(HLMCORE) | SDRUI(NBI-HLM-v90-LIB0) | null 2016-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 recieved 2016-09-02 17:22:51,595 INFO [63414] HLMCoreAgent:elmName PLM2 2016-09-02 17:22:51,595 INFO [63414] HLMCoreAgent:elmHost 10.48.55.29 2016-09-02 17:22:51,595 INFO [63414] HLMCoreAgent:elmUser administrator 2016-09-02 17:22:51,595 INFO [63414] HLMCoreAgent:elmPass ****** 2016-09-02 17:22:51,595 INFO [63414] HLMCoreAgent:deploymentMode HCS 2016-09-02 17:22:51,595 INFO [63414] HLMCoreAgent:null0_CreateELMRequest opening REST connection to supplied LM 2016-09-02 17:22:51,595 INFO [63414] ELMApi: init, connecting to 10.48.55.29 2016-09-02 17:22:51,595 DEBUG [63414] Got the sslCtx 2016-09-02 17:22:51,595 INFO [63414] Initialized the context 2016-09-02 17:22:51,673 INFO [63414] ELMApi: initialized with connection timeout, connected to 10.48.55.29 2016-09-02 17:22:51,673 INFO [63414] HLMCoreAgent:null0_CreateELMRequest validating connection to LM 2016-09-02 17:22:51,673 DEBUG [63414] ELMApi: validateConnection Called 2016-09-02 17:22:53,546 ERROR [63414] HLMCoreAgent:CreateELMRequest Exception: GET https://10.48.55.29/elm-resources returned a response status of 401 Unauthorized 2016-09-02 17:22:53,548 DEBUG [63414] Agent: sending to [SDRUI] ------- <com.cisco.hcs.HLM.jms.CreateELMResponse> <messageType>CreateELMResponse</messageType> <source> <serviceName>HLM</serviceName> <instance>HLMCORE</instance> </source> <destination> <serviceName>SDRUI</serviceName> <instance>NBI-HLM-v90-LIB0</instance> </destination> <sessionID>06e919ba-1c30-47bb-b72d-a4a0a1ca049c</sessionID> <fault>true</fault> <exception> <detailMessage>GET https://10.48.55.29/elm-resources returned a response status of 401 Unauthorized</detailMessage> <stackTrace> <trace>com.cisco.hcs.HLM.core.HLMCoreAgent$null0_CreateELMRequest.fire(HLMCoreAgent.java:363)</trace>
PLM OS 관리자 사용자 ID 및 비밀번호를 추가합니다.
HLM은 PLM에 연결할 수 있지만 PLM은 호환되지 않는 버전으로 다시 회신합니다.
2016-09-05 11:53:19,131 INFO [63394] HLMCoreAgent:null0_CreateELMRequest is fired... 2016-09-05 11:53:19,131 INFO [63394] HLMCoreAgent:null0_CreateELMRequest recieved 2016-09-05 11:53:19,132 INFO [63394] HLMCoreAgent:elmName PLM11 2016-09-05 11:53:19,132 INFO [63394] HLMCoreAgent:elmHost 10.48.53.120 2016-09-05 11:53:19,132 INFO [63394] HLMCoreAgent:elmUser admin 2016-09-05 11:53:19,132 INFO [63394] HLMCoreAgent:elmPass ****** 2016-09-05 11:53:19,132 INFO [63394] HLMCoreAgent:deploymentMode HCS 2016-09-05 11:53:19,132 INFO [63394] HLMCoreAgent:null0_CreateELMRequest opening REST connection to supplied LM 2016-09-05 11:53:19,132 INFO [63394] ELMApi: init, connecting to 10.48.53.120 2016-09-05 11:53:19,132 DEBUG [63394] Got the sslCtx 2016-09-05 11:53:19,132 INFO [63394] Initialized the context 2016-09-05 11:53:19,206 INFO [63394] ELMApi: initialized with connection timeout, connected to 10.48.53.120 2016-09-05 11:53:19,206 INFO [63394] HLMCoreAgent:null0_CreateELMRequest validating connection to LM 2016-09-05 11:53:19,206 DEBUG [63394] ELMApi: validateConnection Called 2016-09-05 11:53:19,457 DEBUG [63394] ELMApi: connection Validated 2016-09-05 11:53:19,457 DEBUG [63394] ELMApi: getELMReg Called 2016-09-05 11:53:19,560 DEBUG [63394] ELMApi: getELMVer Called 2016-09-05 11:53:19,667 DEBUG [63394] HLMCoreAgent:null0_createELMRequest LM PLM11 version is 11.0.1.10000-2 2016-09-05 11:53:19,667 DEBUG [63394] hlmSDRUtil.createELM 2016-09-05 11:53:19,669 DEBUG [63394] hlmSDRUtil.getHCMFDeploymentMode 2016-09-05 11:53:19,669 DEBUG [63394] hlmSDRUtil.beginTransaction 2016-09-05 11:53:19,670 DEBUG [63394] hlmSDRUtilcommitTransaction 2016-09-05 11:53:19,671 DEBUG [63394] hlmSDRUtil.beginTransaction 2016-09-05 11:53:19,672 INFO [63394] LM version is 11.0.1.10000-2 2016-09-05 11:53:19,673 ERROR [63394] hlmSDRUtil.createELM: SDR exception(SDRSyncSession): null 2016-09-05 11:53:19,673 DEBUG [63394] hlmSDRUtil.rollbackTransaction 2016-09-05 11:53:19,673 ERROR [63394] HLMCoreAgent:CreateELMRequest Exception: Attribute TypeELMVersion is required.
추가된 PLM 릴리스가 HCM-F에서 지원되며 HCS 호환성 매트릭스를 참조하는지 확인합니다.