排除PCA 11上所示的非思科裝置故障

簡介

本文描述如何在新增Cisco Unified Communications Manager(CUCM)和Prime License Manager(PLM)時修復庫存Prime合作保證(PCA)問題。 資產顯示裝置為非思科 而它是CUCM應用程式或PLM。

作者：Michal Myszor和Andrea Cingolani，思科TAC工程師。

必要條件 

需求

本文件沒有特定需求。

採用元件

本文檔適用於：

• PCA 11.X託管服務提供商模式(MSP)
• 託管合作調解履行(HCM-F)10.6.X
• 思科整合通訊管理員(CUCM)11.5.X
• 獨立PLM 11.5.X

本文中的資訊是根據特定實驗室環境內的裝置所建立。文中使用到的所有裝置皆從已清除（預設）的組態來啟動。如果您的網路正在作用，請確保您已瞭解任何指令可能造成的影響。

問題

當PCA無法根據SNMP查詢確定裝置型別時，CUCM裝置在資產頁面或裝置檢視中顯示為非思科。

PCA清單顯示：

裝置360檢視上也顯示相同的內容：

AccessLevelDiscovery日誌顯示：

12-Sep-2017|15:25:43.003|DEBUG|AccessLevelDiscovery|pool-4-thread-4|work() : Starting Access Level Discovery for device  10.48.55.29
12-Sep-2017|15:25:43.003|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.AbstractDiscoveryStage|updateStatusReason|41| Later Error Index for device 10.48.55.29 is 1022 Old Message 
12-Sep-2017|15:25:43.003|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.AbstractDiscoveryStage|updateStatusReason|94| Error Index for device 10.48.55.29 is 1022 New Message Discovery in progress.
12-Sep-2017|15:25:43.003|DEBUG|AccessLevelDiscovery|pool-4-thread-4|probeAccessLevel() : Started for device  10.48.55.29
12-Sep-2017|15:25:43.003|DEBUG|AccessLevelDiscovery|pool-4-thread-4|probeAccessLevel() : Matching credentials for  10.48.55.29
12-Sep-2017|15:25:43.003|ERROR|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceAccessLevelDiscovery$MyWorkItem|getFinalDeviceCredentialsList|709| Ignoring the DEFAULT profile as the snmp community string is not provided.
12-Sep-2017|15:25:43.005|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceAccessLevelDiscovery$MyWorkItem|getFinalDeviceCredentialsList|760| probeAccessLevel() : CmDevice Credentials List size : 0
12-Sep-2017|15:25:43.006|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceAccessLevelDiscovery$MyWorkItem|probeAccessLevel|231| Before classificationOfDeviceType,  device credential id is 6429244
12-Sep-2017|15:25:43.007|DEBUG|AccessLevelDiscovery|pool-4-thread-4|probeAccessLevel() : isDeviceTypeReDiscoveryEnabled flag has set to true or mode is MSP -  10.48.55.29  device type is re-initilize to Unknown.
12-Sep-2017|15:25:43.007|DEBUG|AccessLevelDiscovery|pool-4-thread-4|probeAccessLevel() : ******* CmDevice Type Classification - STARTS [ 10.48.55.29 ]*******
12-Sep-2017|15:25:43.007|DEBUG|AccessLevelDiscovery|pool-4-thread-4|probeAccessLevel() : DeviceType is null/Other/Unknown for device  10.48.55.29
12-Sep-2017|15:25:43.007|DEBUG|AccessLevelDiscovery|pool-4-thread-4|probeAccessLevel() : Running device type classification for device  10.48.55.29
12-Sep-2017|15:25:43.007|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceTypeGeneratorManager|getDeviceType|167| getDeviceType() : For device 10.48.55.29 - Find the device Type
12-Sep-2017|15:25:43.007|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceTypeGeneratorManager|getDeviceType|169| getDeviceType() : For device 10.48.55.29; DC PROFILE NAME : 10.48.55.29
12-Sep-2017|15:25:43.007|INFO |AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceTypeGeneratorManager|getDeviceType|217| DC Id: 6429244
12-Sep-2017|15:25:43.008|INFO |AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.access.DeviceUtil|getSysOID|759| DeviceUtil.getSysOID:Before invoking PAL for SysOID10.48.55.29
12-Sep-2017|15:25:43.077|INFO |AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.access.DeviceUtil|getSysOID|766| DeviceUtil.getSysOID:After involking PAL: sysOID =1.3.6.1.4.1.9.1.1348 Ip Address 10.48.55.29
12-Sep-2017|15:25:43.107|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceTypeGeneratorManager|getDeviceType|240| getDeviceType(): SysOID and SysDescr are fetched from device 10.48.55.29
12-Sep-2017|15:25:43.107|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceTypeGeneratorManager|getDeviceType|241| getDeviceType(): SysOID   : 1.3.6.1.4.1.9.1.1348
12-Sep-2017|15:25:43.107|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceTypeGeneratorManager|getDeviceType|242| getDeviceType(): SysDescr : Linux release:2.6.32-431.20.3.el6.x86_64 machine:x86_64
12-Sep-2017|15:25:43.108|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceTypeGeneratorManager|getDeviceType|268| Device type of profile is null
12-Sep-2017|15:25:43.108|INFO |AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.impl.DeviceSwitchType|getDeviceType|17| Checking is Switch Type check for 10.48.55.29
12-Sep-2017|15:25:43.108|INFO |AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.impl.DeviceRouterType|getDeviceType|17| Checking is Router Type for 10.48.55.29
(...)
12-Sep-2017|15:25:44.548|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.impl.DeviceUC500SeriesType|getDeviceType|19| DeviceUC500SeriesType:getDeviceType
12-Sep-2017|15:25:44.548|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.impl.DeviceUC500SeriesType|getDeviceType|26| DeviceGroup- Call Control : DeviceName - Cisco CallManager
12-Sep-2017|15:25:44.637|ERROR|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.impl.DeviceESXType|checkifESX|65| Exception in checkIfESXnull
12-Sep-2017|15:25:44.692|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.impl.DeviceCIMType|checkIfCIM|61| checkIfCIM ()
12-Sep-2017|15:25:45.390|INFO |AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.impl.DeviceSOFTSWITCHType|getDeviceType|42| From DeviceSOFTSWITCHType
12-Sep-2017|15:25:45.390|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.impl.DeviceSOFTSWITCHType|checkIfSoftSwitch|60| checkIfSoftSwitch ()
12-Sep-2017|15:25:46.070|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.impl.DeviceSOFTSWITCHType|getDeviceType|51| Device 10.48.55.29 is not a SOFTSWITCH
12-Sep-2017|15:25:46.070|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.impl.DeviceNonCiscoType|getDeviceType|32| DeviceNonCiscoType: device Type is Non Cisco
12-Sep-2017|15:25:46.139|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceTypeGeneratorManager|getDeviceType|175| probeAccessLevel() : Found DeviceType NONCISCO for device 10.48.55.29
12-Sep-2017|15:25:46.139|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceAccessLevelDiscovery$MyWorkItem|classificationOfDeviceType|339| probeAccessLevel() : ******* CmDevice Type Classification - ENDS *******
12-Sep-2017|15:25:46.140|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceAccessLevelDiscovery$MyWorkItem|probeAccessLevel|244| After classificationOfDeviceType,  device credential id is 6429244
12-Sep-2017|15:25:46.140|DEBUG|AccessLevelDiscovery|pool-4-thread-4|com.cisco.nm.emms.inv.access.core.DeviceAccessLevelDiscovery$MyWorkItem|probeAccessLevel|251| After resetting to original  id,  device credential id  is 6429244
12-Sep-2017|15:25:46.140|DEBUG|AccessLevelDiscovery|pool-4-thread-4|probeAccessLevel() : DC  10.48.55.29  with type  null NOT matched CmDevice  10.48.55.29  with type NONCISCO

解決方案

檢查SNMP服務是否在UC應用上運行。

附註：Cisco CUCM有兩個SNMP服務。

SNMP Master Agent[STARTED]
(...)
Cisco CallManager SNMP Service[STOPPED]  Service Not Activated

Cisco CallManager SNMP服務負責應答思科特定MIB SNMP查詢 

PCA 11.6中已修復SNMP服務關閉，建議關閉SNMP服務：

11-Sep-2017|12:56:52.752|DEBUG|AccessLevelDiscovery|pool-6-thread-10|com.cisco.nm.emms.inv.AbstractDiscoveryStage|updateStatusReason|109| Error Index for device 10.48.50.59 is 1003 New Message SNMP timed out. Probable reasons could be: 1. SNMP service not enabled in the device. 2. SNMP credentials do not match. 3. Firewall settings blocking the port. Refer the Install and Upgrade guide for the exact ports to be unblocked.

問題

PLM裝置在資產頁面上顯示為非思科。

解決方案

1. 在Inventory頁面中選擇PLM伺服器並暫停裝置。
2. 從PCA清單中刪除裝置。
3. 通過命令列介面(CLI)刪除PLM中新增的任何社群字串：

       utils snmp config 1/2c community-string delete

   4.使用作業系統平台憑據(OS PLM CLI)將裝置重新新增到PCA中，並將其新增到HTTP(s)PCA裝置憑據欄位中，如圖所示。