目录

简介

背景信息

缩写

MoP的工作流程

EM中的部署ID、UUID及其关系

预检查

在EM中

在ESC中

在StarOS VNF中

确定UUID不匹配

恢复UUID

清除EM Zookeeper中的挂起请求

简介

本文档介绍在托管StarOS VNF的Ultra-M设置中更正元素管理器(EM)和StarOS虚拟网络功能(VNF)之间的通用唯一ID标识符(UUID)不匹配所需的步骤。

背景信息

Ultra-M是经过预先打包和验证的虚拟化移动数据包核心解决方案，旨在简化VNF的部署。

Ultra-M解决方案包括以下虚拟机(VM)类型：

- 自动IT

- 自动部署

- 超自动化服务(UAS)

- 元素管理器(EM)

- 弹性服务控制器(ESC)

- 控制功能(CF)

- 会话功能(SF)

Ultra-M的高级体系结构和涉及的组件如下图所示：

UltraM体系结构

注意：Ultra M 5.1.x版本用于定义本文档中的过程。

缩写

VNF

虚拟网络功能

CF

控制功能

旧金山

服务功能

ESC

弹性服务控制器

MOP

程序方法

OSD

对象存储磁盘

硬盘

硬盘驱动器

SSD

固态驱动器

VIM

虚拟基础设施管理器

虚拟机

虚拟机

EM

元素管理器

UAS

超自动化服务

UUID

通用唯一ID标识符

MoP的工作流程

EM中的部署ID、UUID及其关系

在Ultra-M设置中有三个主要组件 — ESC、EM和StarOS VNF。EM充当ConfD查询的代理，并代表StarOS VNF发送响应。每个组件都作为VM运行并维护信息。当这三个节点上的VM的数据/状态不匹配时，EM中会出现UUID不匹配警报。ESC向EM发出YANG调用，以获取ConfD数据。ConfD既有配置信息，又有运行数据/状态。EM转换来自ESC的查询并根据需要发送响应。

预检查

在EM中

验证EM是否处于HA模式并显示为master/slave:

ubuntu@vnfd2deploymentem-1:~$ ncs --status | more

vsn: 4.1.1

SMP support: yes, using 2 threads

Using epoll: yes

available modules: backplane,netconf,cdb,cli,snmp,webui

running modules: backplane,netconf,cdb,cli,webui

status: started

cluster status:

mode: master

node id: 6-1528831279

connected slaves: 1

登录到EM并检查EM群集是否正常：

ubuntu@vnfd2deploymentem-1:~$ ncs_cli -u admin -C

admin@scm# show ems

EM VNFM

ID SLA SCM PROXY

---------------------

5 up up up

9 up up up

ubuntu@vnfd2deploymentem-1:~$ ncs_cli -u admin -C

admin@scm# show ncs-state ha

ncs-state ha mode master

ncs-state ha node-id 9-1518035669

ncs-state ha connected-slave [ 5-1518043097 ]

在ESC中

在ESC中，验证与EM的netconf连接已建立：

[admin@vnfm2-esc-0 esc-cli]$ netstat -an | grep 830

tcp        0      0 0.0.0.0:830                 0.0.0.0:*                   LISTEN

tcp        0      0 172.18.181.6:830            172.18.181.11:39266         ESTABLISHED

tcp        0      0 172.18.181.6:830            172.18.181.11:39267         ESTABLISHED

tcp        0      0 :::830                      :::*                        LISTEN

[admin@vnfm2-esc-0 esc-cli]$

从ESC中，确保所有VM都处于活动状态，且服务处于活动状态：

[admin@vnfm2-esc-0 esc-cli]$ ./esc_nc_cli get esc_datamodel | egrep "<vm_name>|<state>"

<state>IMAGE_ACTIVE_STATE</state>

<state>IMAGE_ACTIVE_STATE</state>

<state>IMAGE_ACTIVE_STATE</state>

<state>FLAVOR_ACTIVE_STATE</state>

<state>FLAVOR_ACTIVE_STATE</state>

<state>FLAVOR_ACTIVE_STATE</state>

<state>SERVICE_ACTIVE_STATE</state>

<vm_name>vnfd2-deployment_c1_0_13d5f181-0bd3-43e4-be2d-ada02636d870</vm_name>

<state>VM_ALIVE_STATE</state>

<vm_name>vnfd2-deployment_c4_0_9dd6e15b-8f72-43e7-94c0-924191d99555</vm_name>

<state>VM_ALIVE_STATE</state>

<vm_name>vnfd2-deployment_s2_0_b2cbf15a-3107-45c7-8edf-1afc5b787132</vm_name>

<state>VM_ALIVE_STATE</state>

<vm_name>vnfd2-deployment_s3_0_882cf1ed-fe7a-47a7-b833-dd3e284b3038</vm_name>

<state>VM_ALIVE_STATE</state>

<vm_name>vnfd2-deployment_s5_0_672bbb00-34f2-46e7-a756-52907e1d3b3d</vm_name>

<state>VM_ALIVE_STATE</state>

<vm_name>vnfd2-deployment_s6_0_6f30be77-6b9f-4da8-9577-e39c18f16dfb</vm_name>

<state>VM_ALIVE_STATE</state>

<state>SERVICE_ACTIVE_STATE</state>

<vm_name>vnfd2-deployment_vnfd2-_0_02d1510d-53dd-4a14-9e21-b3b367fef5b8</vm_name>

<state>VM_ALIVE_STATE</state>

<vm_name>vnfd2-deployment_vnfd2-_0_f17989e3-302a-4681-be46-f2ebf62b252a</vm_name>

<state>VM_ALIVE_STATE</state>

<vm_name>vnfd2-deployment_vnfd2-_0_f63241f3-2516-4fc4-92f3-06e45054dba0</vm_name>

<state>VM_ALIVE_STATE</state>

[admin@vnfm2-esc-0 esc-cli]$

在StarOS VNF中

验证vnfm-proxy-agent是否联机：

[local]POD1-VNF2-PGW# show vnfm-proxy-agent status

Thursday June 21 07:25:02 UTC 2018

VNFM Proxy Agent Status:

State        : online

Connected to : 172.18.180.3:2181

Bind Address : 172.18.180.13:38233

VNFM Proxy address count: 3

验证emctrl show活动状态：

[local]POD1-VNF2-PGW# show emctrl status

Thursday June 21 07:25:09 UTC 2018

emctrl status:

emctrl in state: ALIVE

确定UUID不匹配

必须在StarOS VNF和EM之间比较UUID，以识别不匹配。这些步骤列出为了从各个节点获取UUID而要在StarOS VNF和EM中执行的步骤。

在StarOS中，可以从show emctrl vdu list或show card hardware输出获取UUID。

[local]POD1-VNF2-PGW# show emctrl vdu list

Thursday June 21 07:24:28 UTC 2018

Showing emctrl vdu

card[01]: name[CFC_01                                            ] uuid[33C779D2-E271-47AF-8AD5-6A982C79BA62]

card[02]: name[CFC_02                                            ] uuid[E75AE5EE-2236-4FFD-A0D4-054EC246D506]

card[03]: name[SFC_03                                            ] uuid[E1A6762D-4E84-4A86-A1B1-84772B3368DC]

card[04]: name[SFC_04                                            ] uuid[B283D43C-6E0C-42E8-87D4-A3AF15A61A83]

card[05]: name[SFC_05                                            ] uuid[CF0C63DF-D041-42E1-B541-6B15B0BF2F3E]

card[06]: name[SFC_06                                            ] uuid[65344D53-DE09-4B0B-89A6-85D5CFDB3A55]

Incomplete command

[local]POD1-VNF2-PGW# show card hardware | grep -i uuid

Thursday June 21 07:24:46 UTC 2018

UUID/Serial Number      : 33C779D2-E271-47AF-8AD5-6A982C79BA62

UUID/Serial Number      : E75AE5EE-2236-4FFD-A0D4-054EC246D506

UUID/Serial Number      : E1A6762D-4E84-4A86-A1B1-84772B3368DC

UUID/Serial Number      : B283D43C-6E0C-42E8-87D4-A3AF15A61A83

UUID/Serial Number      : CF0C63DF-D041-42E1-B541-6B15B0BF2F3E

UUID/Serial Number      : 65344D53-DE09-4B0B-89A6-85D5CFDB3A55

列出EM中的UUID:

ubuntu@vnfd2deploymentem-1:~$  ncs_cli -u admin -C

admin@scm# show vdus vdu | select vnfci

CONSTITUENT                                                                   MEMORY  STORAGE

DEVICE     DEVICE     ELEMENT      IS                                                        CPU    UTILS   USAGE

ID                ID                            NAME       GROUP      GROUP        INFRA  INITIALIZED  VIM ID                                UTILS  BYTES   BYTES

---------------------------------------------------------------------------------------------------------------------------------------------------------------------

control-function  BOOT_generic_di-chasis_CF1_1  scm-cf-nc  scm-cf-nc  di-chasis    true   true         33c779d2-e271-47af-8ad5-6a982c79ba62  -      -       -

BOOT_generic_di-chasis_CF2_1  scm-cf-nc  scm-cf-nc  di-chasis    true   true         e75ae5ee-2236-4ffd-a0d4-054ec246d506  -      -       -

session-function  BOOT_generic_di-chasis_SF1_1  -          -          di-chasis    true   false        e1a6762d-4e84-4a86-a1b1-84772b3368dc  -      -       -

BOOT_generic_di-chasis_SF2_1  -          -          di-chasis    true   false        b283d43c-6e0c-42e8-87d4-a3af15a61a83  -      -       -

BOOT_generic_di-chasis_SF3_1  -          -          di-chasis    true   false        828281f4-c0f4-4061-b324-26277d294b86  -      -       -

BOOT_generic_di-chasis_SF4_1  -          -          di-chasis    true   false        65344d53-de09-4b0b-89a6-85d5cfdb3a55  -      -       -

从此输出中，您可以看到卡5在EM和StarOS之间存在UUID不匹配：

[local]POD1-VNF2-PGW# show emctrl vdu list

Thursday June 21 07:24:28 UTC 2018

Showing emctrl vdu

.....

card[05]: name[SFC_05                                            ] uuid[CF0C63DF-D041-42E1-B541-6B15B0BF2F3E]

.....

admin@scm# show vdus vdu | select vnfci

CONSTITUENT                                                                   MEMORY  STORAGE

DEVICE     DEVICE     ELEMENT      IS                                                        CPU    UTILS   USAGE

ID                ID                            NAME       GROUP      GROUP        INFRA  INITIALIZED  VIM ID                                UTILS  BYTES   BYTES

---------------------------------------------------------------------------------------------------------------------------------------------------------------------

session-function  .......

BOOT_generic_di-chasis_SF3_1  -          -          di-chasis    true   false        828281f4-c0f4-4061-b324-26277d294b86  -      -       -

......

注意：如果多个卡的UUID不匹配，请确保仅在完成一个卡之后移动到另一个卡。如果您同时尝试多个卡，则可能会遇到与ESC VM索引有关的问题。

恢复UUID

如果UUID不匹配在CF卡中，请确保执行文件系统同步：

[local]VNF2# filesystem synchronize all

如果不匹配的UUID卡为SF且处于活动状态，请执行卡迁移以便使其处于备用状态：

[local]VNF2# card migrate from 4 to 5

如果不匹配的UUID卡为CF且处于活动状态，请执行卡交换使其处于备用状态：

[local]VNF2# card switch from 2 to 1

从EM中的NCS CLI挂起UUID不匹配的卡：

ubuntu@vnfd2deploymentem-1:~$  ncs_cli -u admin -C

admin@scm# suspend-vnfci vdu session-function vnfci BOOT_generic_di-chasis_SF3_1

success true

注意：在某些极少数情况下，来自EM的suspend-vnfci CLI不会在ESC中启动服务更新。  在EM中，日志(/var/log/em/vnfm-proxy/vnfm-proxy.log)显示一条错误消息，指示EM具有待处理的请求并且忽略新请求。要解决此问题，请检查EM zookeeper以查看任何滞留的挂起请求，然后手动清除这些请求。要执行此操作，请参阅本文档的最后一部分“清除EM Zookeeper中的待处理请求（可选）”。

在ESC上的yangesc.log中验证事务已接受，并等待其完成：

####################################################################

#   ESC on vnfm2-esc-0.novalocal is in MASTER state.

####################################################################

[admin@vnfm2-esc-0 ~]$ cd /opt/cisco/esc/esc-confd/esc-cli

[admin@vnfm2-esc-0 esc-cli]$ tail -f /var/log/esc/yangesc.log

19:27:31,333 12-Jun-2018 INFO  Type: SERVICE_ALIVE

19:27:31,333 12-Jun-2018 INFO  Status: SUCCESS

19:27:31,333 12-Jun-2018 INFO  Status Code: 200

19:27:31,333 12-Jun-2018 INFO  Status Msg: Service group deployment completed successfully!

19:27:31,333 12-Jun-2018 INFO  Tenant: core

19:27:31,333 12-Jun-2018 INFO  Deployment ID: 9bcad337-d1f0-463c-8450-de7697b1e104

19:27:31,333 12-Jun-2018 INFO  Deployment name: vnfd2-deployment-1.0.0-1

19:27:31,333 12-Jun-2018 INFO  =====  SEND NOTIFICATION ENDS  =====

07:29:49,510 21-Jun-2018 INFO  ===== GET OPERATIONAL/INFO DATA =====

07:30:32,318 21-Jun-2018 INFO  ===== GET OPERATIONAL/INFO DATA =====

07:36:25,083 21-Jun-2018 INFO  ===== GET OPERATIONAL/INFO DATA =====

07:36:25,628 21-Jun-2018 INFO

07:36:25,628 21-Jun-2018 INFO  =====  CONFD TRANSACTION STARTED  =====

07:36:25,717 21-Jun-2018 INFO

07:36:25,717 21-Jun-2018 INFO  ===== UPDATE SERVICE REQUEST RECEIVED (UNDER TENANT) =====

07:36:25,717 21-Jun-2018 INFO  Tenant name: core

07:36:25,717 21-Jun-2018 INFO  Deployment name: vnfd2-deployment-1.0.0-1

07:36:25,843 21-Jun-2018 INFO

07:36:25,843 21-Jun-2018 INFO  =====  CONFD TRANSACTION ACCEPTED  =====

07:37:04,535 21-Jun-2018 INFO

07:37:04,536 21-Jun-2018 INFO  ===== SEND NOTIFICATION STARTS =====

07:37:04,536 21-Jun-2018 INFO  Type: VM_UNDEPLOYED

07:37:04,536 21-Jun-2018 INFO  Status: SUCCESS

07:37:04,536 21-Jun-2018 INFO  Status Code: 200

07:37:04,536 21-Jun-2018 INFO  Status Msg: VM Undeployed during deployment update, VM name: [vnfd2-deployment_s6_0_6f30be77-6b9f-4da8-9577-e39c18f16dfb]

07:37:04,536 21-Jun-2018 INFO  Tenant: core

07:37:04,536 21-Jun-2018 INFO  Deployment ID: 9bcad337-d1f0-463c-8450-de7697b1e104

07:37:04,536 21-Jun-2018 INFO  Deployment name: vnfd2-deployment-1.0.0-1

07:37:04,536 21-Jun-2018 INFO  VM group name: s6

07:37:04,537 21-Jun-2018 INFO  User configs: 1

07:37:04,537 21-Jun-2018 INFO  VM Source:

07:37:04,537 21-Jun-2018 INFO      VM ID: cf0c63df-d041-42e1-b541-6b15b0bf2f3e

07:37:04,537 21-Jun-2018 INFO      Host ID: 47853854d13d80e6d0212dabb0be2e12c12e431bf23d4e0260642594

07:37:04,537 21-Jun-2018 INFO      Host Name: pod1-compute-9.localdomain

07:37:04,537 21-Jun-2018 INFO  =====  SEND NOTIFICATION ENDS  =====

07:37:04,550 21-Jun-2018 INFO

07:37:04,550 21-Jun-2018 INFO  ===== SEND NOTIFICATION STARTS =====

07:37:04,550 21-Jun-2018 INFO  Type: SERVICE_UPDATED

07:37:04,550 21-Jun-2018 INFO  Status: SUCCESS

07:37:04,550 21-Jun-2018 INFO  Status Code: 200

07:37:04,550 21-Jun-2018 INFO  Status Msg: Service group update completed successfully

07:37:04,550 21-Jun-2018 INFO  Tenant: core

07:37:04,550 21-Jun-2018 INFO  Deployment ID: 9bcad337-d1f0-463c-8450-de7697b1e104

07:37:04,550 21-Jun-2018 INFO  Deployment name: vnfd2-deployment-1.0.0-1

07:37:04,550 21-Jun-2018 INFO  =====  SEND NOTIFICATION ENDS  =====

07:41:55,912 21-Jun-2018 INFO  ===== GET OPERATIONAL/INFO DATA =====

取消部署VM并更新服务后，恢复已暂停的卡：

admin@scm# resume-vnfci vdu session-function vnfci BOOT_generic_di-chasis_SF3_1

success true

从yangesc.log确认VM已重新部署且处于活动状态：

####################################################################

#   ESC on vnfm2-esc-0.novalocal is in MASTER state.

####################################################################

[admin@vnfm2-esc-0 ~]$ cd /opt/cisco/esc/esc-confd/esc-cli

[admin@vnfm2-esc-0 esc-cli]$ tail -f /var/log/esc/yangesc.log

07:41:55,912 21-Jun-2018 INFO  ===== GET OPERATIONAL/INFO DATA =====

07:41:56,412 21-Jun-2018 INFO

07:41:56,413 21-Jun-2018 INFO  =====  CONFD TRANSACTION STARTED  =====

07:41:56,513 21-Jun-2018 INFO

07:41:56,513 21-Jun-2018 INFO  ===== UPDATE SERVICE REQUEST RECEIVED (UNDER TENANT) =====

07:41:56,513 21-Jun-2018 INFO  Tenant name: core

07:41:56,513 21-Jun-2018 INFO  Deployment name: vnfd2-deployment-1.0.0-1

07:41:56,612 21-Jun-2018 INFO

07:41:56,612 21-Jun-2018 INFO  =====  CONFD TRANSACTION ACCEPTED  =====

07:43:53,615 21-Jun-2018 INFO

07:43:53,615 21-Jun-2018 INFO  ===== SEND NOTIFICATION STARTS =====

07:43:53,616 21-Jun-2018 INFO  Type: VM_DEPLOYED

07:43:53,616 21-Jun-2018 INFO  Status: SUCCESS

07:43:53,616 21-Jun-2018 INFO  Status Code: 200

07:43:53,616 21-Jun-2018 INFO  Status Msg: VM Deployed in a deployment update. VM name: [vnfd2-deployment_s6_0_23cc139b-a7ca-45fb-b005-733c98ccc299]

07:43:53,616 21-Jun-2018 INFO  Tenant: core

07:43:53,616 21-Jun-2018 INFO  Deployment ID: 9bcad337-d1f0-463c-8450-de7697b1e104

07:43:53,616 21-Jun-2018 INFO  Deployment name: vnfd2-deployment-1.0.0-1

07:43:53,616 21-Jun-2018 INFO  VM group name: s6

07:43:53,616 21-Jun-2018 INFO  User configs: 1

07:43:53,616 21-Jun-2018 INFO  VM Source:

07:43:53,616 21-Jun-2018 INFO      VM ID: 637547ad-094e-4132-8613-b4d8502ec385

07:43:53,616 21-Jun-2018 INFO      Host ID: 47853854d13d80e6d0212dabb0be2e12c12e431bf23d4e0260642594

07:43:53,616 21-Jun-2018 INFO      Host Name: pod1-compute-9.localdomain

07:43:53,616 21-Jun-2018 INFO  =====  SEND NOTIFICATION ENDS  =====

07:44:20,170 21-Jun-2018 INFO

07:44:20,170 21-Jun-2018 INFO  ===== SEND NOTIFICATION STARTS =====

07:44:20,170 21-Jun-2018 INFO  Type: VM_ALIVE

07:44:20,170 21-Jun-2018 INFO  Status: SUCCESS

07:44:20,170 21-Jun-2018 INFO  Status Code: 200

07:44:20,170 21-Jun-2018 INFO  Status Msg: VM_Alive event received during deployment update, VM ID: [vnfd2-deployment_s6_0_23cc139b-a7ca-45fb-b005-733c98ccc299]

07:44:20,170 21-Jun-2018 INFO  Tenant: core

07:44:20,170 21-Jun-2018 INFO  Deployment ID: 9bcad337-d1f0-463c-8450-de7697b1e104

07:44:20,170 21-Jun-2018 INFO  Deployment name: vnfd2-deployment-1.0.0-1

07:44:20,170 21-Jun-2018 INFO  VM group name: s6

07:44:20,170 21-Jun-2018 INFO  User configs: 1

07:44:20,170 21-Jun-2018 INFO  VM Source:

07:44:20,170 21-Jun-2018 INFO      VM ID: 637547ad-094e-4132-8613-b4d8502ec385

07:44:20,170 21-Jun-2018 INFO      Host ID: 47853854d13d80e6d0212dabb0be2e12c12e431bf23d4e0260642594

07:44:20,170 21-Jun-2018 INFO      Host Name: pod1-compute-9.localdomain

07:44:20,170 21-Jun-2018 INFO  =====  SEND NOTIFICATION ENDS  =====

07:44:20,194 21-Jun-2018 INFO

07:44:20,194 21-Jun-2018 INFO  ===== SEND NOTIFICATION STARTS =====

07:44:20,194 21-Jun-2018 INFO  Type: SERVICE_UPDATED

07:44:20,194 21-Jun-2018 INFO  Status: SUCCESS

07:44:20,194 21-Jun-2018 INFO  Status Code: 200

07:44:20,194 21-Jun-2018 INFO  Status Msg: Service group update completed successfully

07:44:20,194 21-Jun-2018 INFO  Tenant: core

07:44:20,194 21-Jun-2018 INFO  Deployment ID: 9bcad337-d1f0-463c-8450-de7697b1e104

07:44:20,194 21-Jun-2018 INFO  Deployment name: vnfd2-deployment-1.0.0-1

07:44:20,194 21-Jun-2018 INFO  =====  SEND NOTIFICATION ENDS  =====

再次比较StarOS和EM中的UUID，确认已修复不匹配问题：

admin@scm# show vdus vdu | select vnfci

CONSTITUENT                                                                   MEMORY  STORAGE

DEVICE     DEVICE     ELEMENT      IS                                                        CPU    UTILS   USAGE

ID                ID                            NAME       GROUP      GROUP        INFRA  INITIALIZED  VIM ID                                UTILS  BYTES   BYTES

---------------------------------------------------------------------------------------------------------------------------------------------------------------------

control-function  BOOT_generic_di-chasis_CF1_1  scm-cf-nc  scm-cf-nc  di-chasis    true   true         33c779d2-e271-47af-8ad5-6a982c79ba62  -      -       -

BOOT_generic_di-chasis_CF2_1  scm-cf-nc  scm-cf-nc  di-chasis    true   true         e75ae5ee-2236-4ffd-a0d4-054ec246d506  -      -       -

session-function  BOOT_generic_di-chasis_SF1_1  -          -          di-chasis    true   false        e1a6762d-4e84-4a86-a1b1-84772b3368dc  -      -       -

BOOT_generic_di-chasis_SF2_1  -          -          di-chasis    true   false        b283d43c-6e0c-42e8-87d4-a3af15a61a83  -      -       -

BOOT_generic_di-chasis_SF3_1  -          -          di-chasis    true   false        637547ad-094e-4132-8613-b4d8502ec385  -      -       -

BOOT_generic_di-chasis_SF4_1  -          -          di-chasis    true   false        65344d53-de09-4b0b-89a6-85d5cfdb3a55  -      -       -

[local]POD1-VNF2-PGW# show emctrl vdu list

Thursday June 21 09:09:02 UTC 2018

Showing emctrl vdu

card[01]: name[CFC_01                                            ] uuid[33C779D2-E271-47AF-8AD5-6A982C79BA62]

card[02]: name[CFC_02                                            ] uuid[E75AE5EE-2236-4FFD-A0D4-054EC246D506]

card[03]: name[SFC_03                                            ] uuid[E1A6762D-4E84-4A86-A1B1-84772B3368DC]

card[04]: name[SFC_04                                            ] uuid[B283D43C-6E0C-42E8-87D4-A3AF15A61A83]

card[05]: name[session-function/BOOT_generic_di-chasis_SF3_1     ] uuid[637547AD-094E-4132-8613-B4D8502EC385]

card[06]: name[SFC_06                                            ] uuid[65344D53-DE09-4B0B-89A6-85D5CFDB3A55]

Incomplete command

[local]POD1-VNF2-PGW#

[local]POD1-VNF2-PGW#

[local]POD1-VNF2-PGW#

[local]POD1-VNF2-PGW# show card hardware | grep -i uuid

Thursday June 21 09:09:11 UTC 2018

UUID/Serial Number      : 33C779D2-E271-47AF-8AD5-6A982C79BA62

UUID/Serial Number      : E75AE5EE-2236-4FFD-A0D4-054EC246D506

UUID/Serial Number      : E1A6762D-4E84-4A86-A1B1-84772B3368DC

UUID/Serial Number      : B283D43C-6E0C-42E8-87D4-A3AF15A61A83

UUID/Serial Number      : 637547AD-094E-4132-8613-B4D8502EC385

UUID/Serial Number      : 65344D53-DE09-4B0B-89A6-85D5CFDB3A55

清除EM Zookeeper中的挂起请求

注意：此操作为可选操作。

访问zookeeper:

ubuntu@ultramvnfm1em-0:~$ /opt/cisco/usp/packages/zookeeper/current/bin/zkCli.sh

<snip>

[zk: localhost:2181(CONNECTED) 0]

列出待处理请求：

[zk: localhost:2181(CONNECTED) 0] ls /request

删除所有列出的请求：

[zk: localhost:2181(CONNECTED) 0] rmr /request/request00000000xx

清除所有挂起请求后，再次重新启动挂起请求。