什么是 ActiveIQ Unified Manager 的记录文件以及如何解析这些文件以进行故障排除？

适用场景

Active IQ Unified Manager (AIQUM)

问题解答

在ActiveIQ Unified Manager中触发轮询周期以从集群模式ONTAP操作系统收集数据时、系统会创建录制文件。

• 录制文件会捕获ActiveIQ Unified Manager实际从集群收到的原始API数据。
• 每次执行清单轮询时都会创建Foundation录制文件。
  • 默认情况下、轮询每5分钟一次。
• 性能录制文件会捆绑到一个 ‘每天录制一个内容’zip文件中。
  • 性能录制文件中的每个录制文件最多包含5个轮询周期样本(编号文件夹)。
• 记录文件提供了一个或多个"Sample．log"文件，用于记录轮询周期成功或失败的状态。

记录文件命名约定： LogType_CLUSTERNAME.corp.company.org_datasourceid_year_month_day_HR_MIN_SEC_XXX.zip
"Sample．log"文件命名约定： log_LogType_CLUSTERNAME.corp.company.org_91_year_month_day_HR_MIN_SEC_XXX.sample.log

• 记录"sSample．log"通常位于"root"文件夹中，但也可以位于Number文件夹中；请检查这两个文件夹。

 

如何在
支持包中查找录制文件在支持包中、录制文件位于以下文件夹中： support_Bundle日期_HR_min_SEC\acac购置\Recording

查找 在观察问题描述之日创建的存储性能录制文件。
示例： netappstorageperformance_CLUSTER01.corp.company.org_01_2019_06_09_08_37_21_665.zip

• 如何查找Sample.log文件
  • 检查根文件夹或编号文件夹以识别Sample.log文件。
  • 在任何文本编辑器中打开sample.log文件。   
  • 此示例文件将告诉您性能采集是成功还是失败。
  • 如果失败、则会在sample.log文件中捕获此错误。

 

为了方便起见、以下是 有关netappFoundation和netappstoragePerformance的录制文件结构示例。

网络基础：

netappFoundation _xx.xx.xx_3_2019_05_30_11_51_22_243

├───1559242272012
│      description.xml
│      log_netappfoundation_xx.xx.xx.xx_91_2019_05_30_11_51_12_075_iterator_response_times.txt
│      
│      
      
      
      recording_netappfoundation_xx.xx.xx.xx_91_2019_05_30_11_51_12_074_netappfoundation.dat│


       
       description.xml
       log_netappfoundation_xx.xx.xx.xx_91_2019_05_30_11_51_12_012_sample.log│netappdata_netappfoundation_xx.xx.xx.xx_91_2019_05_30_11_51_21_337_3.xml│log_netappfoundation_xx.xx.xx.xx_91_2019_05_30_11_51_12_076_zapi_attributes.txt│└───log_netappfoundation_xx.xx.xx.xx_91_2019_05_30_11_51_22_165_poll_time.txt root configuration model_netappfoundation_xx.xx.xx.xx_91_2019_05_30_11_51_21_306.xml

netappstorage性能：

netappstoragePerformance _xx.xx.xx.xx_3_2019_05_30_00_28_01_556
├───1559200078025
│      description.xml
│      log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_08_06_225_iterator_response_times.txt
│      log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_08_06_226_zapi_attributes.txt
│      log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_08_09_441_poll_time.txt
│      log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_08_13_303_poll_time.txt
│      
      
      
      recording_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_08_06_224_netappstorageperformance.dat│


      163185_000300_1559199900886_0270000.ccma.gz│netappfoundation_xx.xx.xx.xx_3_2019_05_30_00_06_28_852_copy.zip│log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_08_15_142_poll_time.txt│├───1559200378012│log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_08_25_691_poll_time.txt
│       163185_000300_15591999008686_0270000.CCMA.MD5
│      163185_000300_15591999008686_0270000.CCMA.meta
│      163382_000300_1559199900552_0282000.ccma.gz
│      1633382_000300_1559199900552_0282000.CCMA.MD5
│      1633382_000300_1559199900552_0282000.CCMA.meta
│      
      
      
││      
│log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_12_59_621_ocie_report_times.txt      
│log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_02_120_poll_time.txt      
│      
      
      
      
      
      perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_735_WaflCounter.csv│description.xml│log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_12_58_014_iterator_response_times.txt│perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_555_WorkloadDetailCounter.csv│perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_651_LifCounter.csv│perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_718_NFSv3Counter.csv│perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_462_WorkloadQueueDBladeCounter.csv perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_495_WorkloadQueueNBladeCounter.csv perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_518_ResourceCounter.csv log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_12_58_015_zapi_attributes.txt
│      
│      
│      
│      perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_860_AggregateCounter.csv
│      perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_914_HostadapterCounter.csv
│      perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_920_NicCommonCounter.csv
│perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_763_ProcessorCounter.csv      
│perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_784_DiskConfigCounter.csv      
│perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_796_DiskCounter.csv      
│perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_01_983_CifsCounter.csv      
│      perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_02_077_ResourceHeadRoomAggrCounter.csv
│      recording_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_12_58_013_netappstorageperformance.dat perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_02_050_ResourceHeadRoomCPUCounter.csv perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_02_011_NodeCounter.csv perfdata_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_13_02_034_ExtCacheObjCounter.csv
│
├───<已截断3个编号文件夹输出>
│
└───根
       配置
       description.xml
       log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_07_58_025_sample.log
       log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_12_58_012_sample.log
       log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_17_58_031_sample.log
       log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_22_58_054_sample.log
       log_netappstorageperformance_xx.xx.xx.xx_91_2019_05_30_00_27_58_014_sample.log

追加信息

在存储性能记录中、是 从集群下载的CCMA文件的副本。

• 这些CCMA文件不可供用户读取、只能使用专用软件工具进行解析。  CCMA文件包含集群中的原始性能数据。
• 此CCMA文件位于 存储性能 记录中的UNIX时间戳文件夹(也称为"编号"文件夹)内。
• 在每个编号文件夹中、集群中的每个节点都应有一个CCMA.gz、一个CCMA.MD5和一个CCMA.meta文件。
  • 如果缺少这些文件中的任何一个、则可能意味着Unified Manager未从 其中一个集群节点收到CCMA文件集合。
• 为了节省支持包中的空间、在  全天捕获的众多性能录像中、每个每日性能录像文件仅包含5个CCMA文件。