版本数据库损坏

H3CCAS-E0509H01版本说明书Copyright2018新华三技术有限公司版权所有,保留一切权利.
非经本公司书面许可,任何单位和个人不得擅自摘抄、复制本文档内容的部分或全部,并不得以任何形式传播.
本文档中的信息可能变动,恕不另行通知.
i目录1版本信息·························································································································11.
1版本号·························································································································11.
2历史版本信息················································································································12软件运行环境···················································································································22.
1管理服务器配置要求·······································································································22.
2业务服务器配置要求·······································································································22.
3客户端配置要求·············································································································23版本使用限制···················································································································24注意事项·························································································································35版本特性说明···················································································································46版本变更说明···················································································································56.
1特性变更说明················································································································56.
1.
1E0509H01版本特性变更························································································56.
1.
2E0509版本特性变更······························································································56.
1.
3C0508版本特性变更·····························································································56.
1.
4E0506版本特性变更······························································································56.
1.
5E0503版本特性变更······························································································66.
1.
6E0502版本特性变更······························································································66.
1.
7E0501版本特性变更······························································································66.
2操作方式变更说明··········································································································66.
2.
1E0509H01版本操作方式变更··················································································66.
2.
2E0509版本操作方式变更························································································66.
2.
3C0508版本操作方式变更·······················································································66.
2.
4E0506版本操作方式变更························································································66.
2.
5E0503版本操作方式变更························································································76.
2.
6E0502版本操作方式变更························································································76.
2.
7E0501版本操作方式变更························································································77存在问题与规避措施··········································································································78解决问题列表·················································································································108.
1E0509H01版本解决问题列表·························································································108.
1.
1虚拟机状态异常问题····························································································108.
1.
2UNIC-NIC-10GE-2P-520F-B2网卡无法识别问题·······················································108.
1.
3信息泄露漏洞CNVD-2017-32023问题····································································108.
1.
4页面跳转问题·····································································································108.
2E0509版本解决问题列表······························································································11ii8.
2.
1Broadcom部分网卡不支持SR-IOV功能问题····························································118.
2.
2虚拟机镜像被删除问题·························································································118.
2.
3删除模板报未知错误问题······················································································118.
2.
4Nova插件挂载磁盘不兼容问题··············································································118.
3C0508版本解决问题列表······························································································118.
3.
1日志分区占满问题·······························································································118.
3.
2File安全漏洞问题·······························································································118.
3.
3TLS1.
2握手漏洞问题··························································································118.
3.
4OpenSSL安全漏洞问题·······················································································118.
3.
5Emulex10GbE网卡故障问题················································································128.
4E0506版本解决问题列表······························································································128.
4.
1Tomcat性能下降问题··························································································128.
4.
2虚拟机未故障迁移问题·························································································128.
4.
3VMware上安装CAS问题·····················································································128.
4.
4虚拟机无法迁移问题····························································································128.
4.
5Web页面应用渗透漏洞问题··················································································128.
4.
6数据库连接错误问题····························································································128.
4.
7虚拟机异常状态问题····························································································128.
4.
8导出虚拟机OVF模板超时问题··············································································138.
4.
9ApacheTomcat安全漏洞问题···············································································138.
5E0503版本解决问题列表······························································································138.
5.
1主机Fence重启问题···························································································138.
5.
2动态聚合UP慢问题····························································································138.
5.
3WEB页面应用渗透漏洞问题··················································································138.
5.
4性能监控无数据问题····························································································138.
5.
5集群阻塞问题·····································································································138.
5.
6主机加入集群失败问题·························································································138.
5.
7两节点零存储环境配置仲裁IP无法启动的问题··························································148.
5.
8零存储和S1020V共用时零存储无法注册License的问题············································148.
5.
9零存储做数据平衡导致根分区满的问题····································································148.
5.
10零存储Admin进程退出引发CAS集群重启的问题····················································148.
5.
11零存储进程异常退出问题····················································································148.
6E0502版本解决问题列表······························································································148.
6.
1BFA驱动异常问题······························································································148.
6.
2CPU热添加导致虚拟机挂死问题············································································148.
6.
3Nova插件无法获取存储池列表问题········································································148.
6.
4虚拟机拉取组播流量异常问题················································································148.
7E0501版本解决问题列表······························································································15iii9技术支持·······················································································································1510相关资料·····················································································································1510.
1相关资料清单············································································································1510.
2资料获取方法············································································································1511版本升级操作指导·········································································································1511.
1版本升级介绍············································································································1511.
1.
1CAS1.
0升级到CAS5.
0介绍················································································1511.
1.
2CAS2.
0升级到CAS5.
0介绍················································································1611.
1.
3CAS3.
0升级到CAS5.
0介绍················································································1711.
1.
4重要版本介绍···································································································1711.
1.
5CAStools介绍··································································································1811.
1.
6升级环境介绍···································································································1811.
1.
7升级方式介绍···································································································1811.
1.
8升级脚本参数介绍·····························································································1811.
1.
9升级日志文件介绍·····························································································2111.
1.
10升级注意事项··································································································2111.
1.
11双机热备环境升级注意事项················································································2211.
2版本升级操作步骤······································································································2211.
2.
1升级前准备······································································································2311.
2.
2暂停业务·········································································································2411.
2.
3升级预检查······································································································2411.
2.
4升级版本·········································································································2611.
2.
5升级验收检查···································································································2711.
2.
6重启主机·········································································································2811.
2.
7检查版本·········································································································2811.
2.
8恢复业务·········································································································2812软件注册说明···············································································································3112.
1License获取方法·······································································································3112.
1.
1获取主机文件···································································································3112.
1.
2获取License文件·····························································································3412.
2注册方法··················································································································34附录ACAStools和CAS版本对应关系表··············································································35附录BCAS系统必要的端口表·····························································································35附录CCAS包含驱动列表··································································································36附录DCAS版本与合作厂家版本配套表················································································37i表目录表1历史版本信息表1表2管理服务器配置要求2表3业务服务器配置要求2表4CAS特性列表.
411版本信息1.
1版本号全称:H3CCAS云计算管理平台简称:H3CCAS5.
0(E0509H01)[注]:在CAS配置管理界面点击右上角的"关于"链接,在弹出的[关于]窗口中可以查看版本号.

软件版本校验和:(1)升级包CAS-E0509H01-Upgrade.
tar.
gz(d67120b375a77f52464234dd9a155376)(2)Plug-inplugin-E0509H01.
tar(067543cc648154f89dcb544811d0e02f)1.
2历史版本信息表1历史版本信息表版本号基础版本号发布日期版本兼容列表备注CAS-E0509H01CAS-E05092018-04-03CAS-E0509CAS-C0508CAS-E0506CAS-E0503CAS-E0502CAS-E0501解决问题CAS-E0509CAS-C05082018-02-09CAS-C0508CAS-E0506CAS-E0503CAS-E0502CAS-E0501增加特性和解决问题CAS-C0508CAS-E05062017-12-28CAS-E0506CAS-E0503CAS-E0502CAS-E0501增加特性和解决问题CAS-E0506CAS-E05032017-11-27CAS-E0503CAS-E0502CAS-E0501增加特性和解决问题CAS-E0503CAS-E05022017-08-28CAS-E0502CAS-E0501解决问题CAS-E0502CAS-E05012017-07-24CAS-E0501解决问题CAS-E0501首次发布2017-06-28首次发布首个版本22软件运行环境2.
1管理服务器配置要求表2管理服务器配置要求硬件名称规格参数CPU支持Intel-VT或AMD-V内存>16GB硬盘≥200GB网卡≥2个千兆以太网口2.
2业务服务器配置要求表3业务服务器配置要求硬件名称规格参数CPU支持Intel-VT或AMD-V内存>16GB硬盘≥200GB网卡≥4个千兆以太网口2.
3客户端配置要求H3CCAS云计算管理平台基于标准的Web页面开发,用户访问时无需安装任何客户端,可以直接通过Web浏览器(如GoogleChrome、MozillaFirefox等)进行访问.
3版本使用限制(1)安装CAS软件的服务器的CPU必须支持硬件辅助虚拟化技术,如Intel-VT或AMD-V.
(2)USB虚拟化是指将服务器上的USB分配给某个虚拟机使用,但不支持虚拟机的迁移,不支持USBoverNetwork.
(3)H3CCAS软件FCoE特性当前已验证支持的均为刀片服务器网卡,型号如下:HPFlexFabric20Gb2-port630FLBAdapterHPFlexFabric10Gb2-port536FLBAdapterHPFlexFabric10Gb2-port534FLBAdapter(4)CIC兼容vCenter增强功能,对vCenter4.
1不支持增加虚拟机操作.
(5)CIC兼容vCenter增强功能,对vCenter6.
0不支持集群性能监控的内存百分比数据显示.
(6)暂不支持配置下面网卡的服务器上新装E0502,型号如下:vendor:14E4device:1639BroadcomLimitedNetXtremeIIBCM5709GigabitEthernetvendor:14E4device:163aBroadcomLimitedNetXtremeIIBCM5709SGigabitEthernet3vendor:14E4device:163bBroadcomLimitedNetXtremeIIBCM5716GigabitEthernetvendor:14E4device:163cBroadcomLimitedNetXtremeIIBCM5716SGigabitEthernetvendor:14E4device:164aBroadcomLimitedNetXtremeIIBCM5706GigabitEthernetvendor:14E4device:164cBroadcomLimitedNetXtremeIIBCM5708GigabitEthernetvendor:14E4device:16aaBroadcomLimitedNetXtremeIIBCM5706SGigabitEthernetvendor:14E4device:16acBroadcomLimitedNetXtremeIIBCM5708SGigabitEthernet4注意事项(1)CVM作为纯CVK使用后,不能再次作为CVM使用,需要重新安装才能作为CVM管理平台.
(2)CASE0506版本和ONEStorR315P01版本适配时,升级的时候会有libc6交互,且会有多个节点交互,不能使用并行升级.
(3)存储上将共享文件系统存储池对应的只读权限的LUN恢复为可读写权限后,需要将此存储池从主机上删除掉,重新添加.
(4)与其他产品的配套表,参考其他产品的版本说明书.
(5)如果有用CVK模拟的NFSServer,需要先删除以CVK模拟NFSServer的NFS类型存储池再升级E0501及之后的CAS5.
0版本.
(6)如果之前版本携带了零存储,那么需要先升级到E0306H11版本过渡,然后再升级到E0501及之后的CAS5.
0版本.
(7)E0501支持Fence不重启功能,安装或升级E0501及后续版本后,若想使用此功能,则需在CVM界面"系统管理"下面的"参数设置"里面设置"共享存储故障隔离"参数为"不重启主机"模式.

从原支持Fence不重启的版本C0305或C0307升级至E0501,需要重新设置下"共享存储故障隔离"参数为"不重启主机"模式才可继续保持Fence不重启功能.
(8)如果CAS2.
0版本中参数配置-系统参数的管理台日志级别设置为调试级别,则升级到5.
0版本时需要手动调整管理台日志级别.
(9)在E0303H02之前的版本如果修改共享文件系统存储池的显示名称,升级E0303H02后的版本,需要在共享文件系统上重新修改一下共享文件系统存储池的显示名称.
(10)双机热备环境,从E0306版本之前版本升级,请重新使能NTP配置.
(11)双机热备安装过程中提示手动输入Mysql分区的大小,可以根据用户的实际使用场景进行设置.
(12)服务器在UEFI模式时,不支持使用PXE服务器安装引导CAS系统盘.
(13)对于虚拟机作为CVM,且CVM管理了CVM虚拟机自己所在CVK主机,从CAS2.
0注册正式License的版本升级到CAS3.
0,需要按照如下步骤操作才能正常登陆CAS管理平台:a.
SSH到CVM虚拟机所在的CVK上,修改CVM虚拟机的XML文件打开串口侦听,使用如下命令编辑虚拟机的XML:virshedit具体是增加如下粗体内容:4b.
SSH到CVM虚拟机内部执行正常关机.
c.
SSH到CVM虚拟机所在的CVK上执行命令启动CVM虚拟机:virshstartd.
登陆CASCVM登陆界面,收集虚拟机Host文件.
e.
到License网站申请设备变更.
f.
CVM重新注册License即可.
(14)凝思操作系统启动必须选择root模式登陆,启动后CAStools才可用,否则,CAStools无法运行.
(15)CentOS6.
5或RedHat6.
5虚拟机,如果需要添加服务器的GPU设备,那么虚拟机安装时,需要选择"Installsystemwithbasicvideodriver"方式安装.
(16)在线迁移虚拟机时,如果虚拟机过忙(写IO每秒钟产生的脏内存大于管理网带宽),会出现虚拟机迁移超时暂停(一直卡在99%)的现象,所以在线迁移虚拟机时,需要设置虚拟机的"迁移超时时长"为0(永不超时),且同时降低虚拟机写IO频率.
(17)与SDNB02版本配套使用SDNvSwitch替换后,CAS中凡是与标准CASvSwitch配合使用的功能都将不可用,比如DRX温暖下线、ACL策略、QoS、网络优先级、端口镜像、NetFlow、DHCP服务等功能.
(18)制作Windows7操作系统的虚拟机模板之前,必须把Windows7操作系统的休眠功能去掉,否则可能会出现休眠后无法唤醒.
(19)当DRS和DPM等功能生效,且正在迁移虚拟机过程中,严禁对集群HA的配置进行变更,否则会造成集群HA状态异常和虚拟机无法正常操作的问题,如果需要禁用集群HA功能,请首先禁用集群的DRS和DPM功能,并等待处于迁移状态的虚拟机完成迁移操作之后,才执行禁用集群HA操作.
(20)对Firefox浏览器支持不完善,使用个别功能时,可能会出现页面显示问题,但不影响正常使用.

(21)在为虚拟机安装操作系统时,请注意使用正版操作系统软件,否则可能出现虚拟机操作系统定期自动关机的情况.
5版本特性说明表4CAS特性列表特性标准版企业版企业增强版DRX(动态资源扩展)虚拟化拓扑应用HA硬件SR-IOVGPU直通GPU资源池虚拟机生命周期管理一键系列大屏监控5资源性能监控大屏监控定制化站点容灾管理(SRM)云彩虹2.
0VxLAN管理平台双机热备兼容VMware虚拟桌面池用户自助服务电子流资源申请与审批流程定制6版本变更说明6.
1特性变更说明6.
1.
1E0509H01版本特性变更无.
6.
1.
2E0509版本特性变更(1)导航树优化6.
1.
3C0508版本特性变更(1)分布式存储ONEStor性能监控(2)服务器组件IPMI状态监控(3)清华大学IPv6虚拟交换转发(4)易用性(5)SNMP告警MIB(6)存储故障虚拟机冻结(7)磁盘加密迁移(8)虚拟防火墙特性6.
1.
4E0506版本特性变更(1)业务网HA(2)告警管理整改(3)电信集采特性(亲和性、双机、CPU上限、模板部署等)(4)Libguestfs(5)CAStools支持FreeBSD操作系统66.
1.
5E0503版本特性变更无.
6.
1.
6E0502版本特性变更无.
6.
1.
7E0501版本特性变更版本首次发布.
(1)CIC优化整改(2)OCFS2Fence不重启(3)HA优化(4)DPDK特性(5)PNUMA和VNUMA(6)内存大页(7)杀毒特性(E0501内核升级后与趋势和360的适配)(8)磁盘预分配(9)磁盘加密(10)单磁盘备份(11)网络USB(12)OVF模板导入(13)云安全安全区域、保密策略(14)广电网定制化需求(15)一键僵尸虚拟机(16)零存储裁剪(老版本带零存储升级上来能用)6.
2操作方式变更说明6.
2.
1E0509H01版本操作方式变更与E0501版本操作方式一致.
6.
2.
2E0509版本操作方式变更与E0501版本操作方式一致.
6.
2.
3C0508版本操作方式变更与E0501版本操作方式一致.
6.
2.
4E0506版本操作方式变更与E0501版本操作方式一致.
76.
2.
5E0503版本操作方式变更与E0501版本操作方式一致.
6.
2.
6E0502版本操作方式变更与E0501版本操作方式一致.
6.
2.
7E0501版本操作方式变更版本首次发布.
7存在问题与规避措施1.
集群HA无法禁用,且虚拟机无法正常操作的问题问题现象:集群HA无法禁用,且虚拟机无法正常操作.
问题产生条件:当集群的DRS或DPM等功能生效,并且虚拟机正在迁移的过程中,对集群HA进行禁用操作.
规避措施:请等待处于迁移状态的虚拟机完成迁移操作之后,再执行禁用集群HA操作.
2.
CIC上浮动桌面健康检测,检测中CAS界面一直为加载中状态问题问题现象:在CIC上对浮动桌面进行健康检测,检测过程中CAS界面一直为加载中状态.
问题产生条件:CIC上部署浮动桌面池,部署完成后进行健康检测.
规避措施:CIC和CAS分别在使用不同的浏览器打开或健康检测时不要切换CAS界面.
3.
单台CVK上运行虚拟机超过50台,不能启用HA服务.
问题现象:单台CVK上运行虚拟机超过50台,HA迁移虚拟机的任务一直挂在99%状态.
问题产生条件:集群启用HA服务,单台CVK上运行虚拟机超过50台.
4.
在E0209上做的CVM备份,升级到E0209之后的版本,发现CVM备份历史为空问题.
问题现象:在E0209版本上做CVM备份,版本升级到E0209之后的版本,再到备份历史页面查看CVM信息,没有CVM的备份信息,在后台备份目录下查看CVM备份文件存在.
问题产生条件:在E0209版本升级后续版本前做CVM备份.
规避措施:在后台CVM备份目录下,通过命令hostname获取主机名,在备份目录下新建一个以主机名命名的目录,将该CVM的备份文件移到新建的目录下.
前台刷新一下备份历史页面就可以显示升级前的CVM的备份信息.
5.
保护模式虚拟机CAStools升级问题问题现象:一些虚拟机模板中的CAStools版本较低且不支持手动/自动升级,通过该模板部署出保护模式虚拟机后,不论通过手动/自动升级方式,都无法将CAStools升级到最新版本.
问题产生条件:通过浮动桌面部署出的保护模式虚拟机,且所用模板安装了不支持手动/自动升级的CAStools.
规避措施:安装较高版本的CAStools,要求此版本必须支持手动/自动升级,并重新制作虚拟机模板.
6.
E0203H01升级到E0301之后版本存在HA偶然性未关闭导致升级中止问题问题现象:已禁用HA条件下,从E0203H01升E0301过程,报错:TheHAofhosts(XXX)hasbeenenabled,PleaseRetryafterdisablingit.
8问题产生条件:从E0203H01升E0301过程.
规避措施:请在CAS管理平台将集群HA先启用,再禁用,然后再尝试升级.
7.
镜像文件在NFS存储池里的虚拟机将不被HA管理问题问题现象:带NFS存储池的老HA版本(E0206之前的版本)的CAS环境升级到E0301之后版本,镜像文件在NFS存储池里的虚拟机将不被HA管理,且虚拟机和主机的绑定关系可能出错.
问题产生条件:带NFS存储池的老HA版本的CAS环境升级到E0301之后版本.
规避措施:通过手工删除再添加NFS存储池,然后点击一键存储清理中的开始扫描按钮,实现数据库存储池信息已经绑定关系的更新.
8.
Windows虚拟机开启内存限制导致无法启动问题问题现象:Windows虚拟机开启内存限制之后启动过程被反复关机无法启动.
问题产生条件:Windows虚拟机配置了比较大的内存,而内存限制却限制了比较小的内存.
规避措施:内存限制时需要考虑服务器的Swap可用大小是否足够,内存限制之后虚拟机被限制的那部分内存都需要交换到Swap,如果Swap可用大小不够,则会影响虚拟机的启动.
9.
升级或安装CAS版本出现Grub安装到哪个磁盘的选项问题问题现象:升级或安装CAS版本时,出现Grub安装到哪个磁盘的选项:1.
/dev/sda(53687MB;iSCSIDisk)2.
/dev/sdb(53687MB;iSCSIDisk)3.
/dev/vda(32212MB;)4.
/dev/vda1(6450MB;/)(Entertheitemsyouwanttoselect,separatedbyspaces.
)GRUBinstalldevices:问题产生条件:CAS虚拟机做CVM时升级到E0303之后的版本,升级环境中出现Grub安装到哪个磁盘的选项.
规避措施:选择安装到根分区所在的磁盘上(/dev/vda).
10.
从存储池中还原备份虚拟机失败问题问题现象:将虚拟机备份到存储池(共享文件系统,NFS、Windows共享等类型的存储池)过程中暂停该存储池,重新激活该存储池后,还原备份虚拟机失败.
问题产生条件:备份虚拟机到存储池(共享文件系统,NFS、Windows共享等类型的存储池)过程中暂停该存储池.
其他虚拟机数据拷贝或转移(如克隆、部署等操作)操作过程中暂停存储池,也存在数据在本地目录下而导致的异常.
规避措施:关闭该存储池(共享文件系统,NFS、Windows共享等类型的存储池),然后执行还原备份虚拟机操作,还原操作完成后,将备份的数据转移到其它地方,在备份管理中重新导入备份数据,再将挂载点目录为空状态时,再启动存储池.
11.
MySQL数据库损坏问题问题现象:升级CAS版本时出现MySQL错误ERROR2002(HY000):Can'tconnecttolocalMySQLserverthroughsocket'/var/run/mysqld/mysqld.
sock'(2),导致升级数据库失败.
规避措施:现场手工执行数据库升级脚本进行处理,操作步骤如下:(1)进入升级盘的解压目录upgrade.
eXXXX执行命令cdupgrade.
eXXXX/package/front.
upgrade/cvm/upgrade,注意上述要修改具体的CAS版本号,如:cdupgrade.
e0306/package/front.
upgrade/cvm/upgrade(2)执行CVM及CIC的升级脚本9执行CVM的数据库升级脚本update_script_cvm.
sh,第一个参数是升级脚本的目录,第二个参数是当前CVM的版本号,以从E0306升级到E0306H13为例,命令如下:shupdate_script_cvm.
sh/root/upgrade.
e0306h13/package/front.
upgrade/cvm/upgrade"V3.
0E0306"执行CIC的数据库升级脚本update_script_cic.
sh,第一个参数是升级脚本的目录,第二个参数是当前CVM的版本号,第三个参数是CVMIP地址,以从E0306升级到E0306H13为例,命令如下:shupdate_script_cic.
sh/root/upgrade.
e0306h13/package/front.
upgrade/cic/upgrade"V3.
0E0306"CVM_IP12.
存储服务器不可访导致模板存储池异常问题问题现象:使用模板存储池进行虚拟机的克隆、迁移、部署等数据操作时,取消主机对存储服务器的访问权限,或中断存储服务器与主机间的链路连接,此时模板存储列表刷新缓慢,需要耐心等待返回结果.
此时查看模板存储池,会处于活动状态,但由于主机无法访问存储服务器,使得模板存储池不可使用,则模板相关的虚拟机克隆、迁移、部署等操作会失败.
若此时恢复主机对存储服务器的正常访问,由于文件系统不能自动感知存储访问恢复正常,模板存储池仍不可用.

上述情况包含的模板存储类型:iSCSI共享目录、FC共享目录、NFS网络文件系统.
规避措施:首先,检查模板存储目录下已有文件的情况,确认其是否有用,若有用,需要备份到其他地方,或者将原有目录重命名,没有用则可以清掉;第二步,恢复主机与存储服务器之间的正常访问,确保主机可读写存储;第三步,在界面模板存储中暂停该模板存储池;第四步,如果文件系统变为只读,则需要进行手工修复和检查;比如采用e2fsck工具及相关工具进行修复;第五步,点击"激活"按钮,重新激活模板存储池.
13.
自动挂载共享存储池失败问题问题现象:虚拟机存储迁移到共享存储时,目标共享存储所在的主机发生重启,重启正常但共享存储还未挂载上目录时,存储迁移任务继续往该存储目录(此时还未挂载成,是本地目录)中拷贝文件,将导致该目录不为空而挂载共享存储池失败.
问题产生条件:虚拟机存储迁移到共享存储时,目标共享存储所在的主机发生重启,重启正常但共享存储还未挂载上目录时.
规避措施:检查原存储池位置处的镜像文件是否存在.
若存在,则表示迁移失败,可手工删除目标位置处的镜像文件,保证存储池挂载点的目录为空,从而不会影响下次共享文件系统的拉起动作,共享存储池挂载成功后,再执行迁移操作;若不存在,则表示迁移成功,手工将目标位置处的镜像文件备份,然后将存储池挂载点的目录清空,从而不会影响下次共享文件系统的拉起动作,共享存储池挂载成功后,再将备份的镜像文件拷贝到目标位置处.
14.
双机热备环境下,启用或禁用模板存储导致CAS管理界面打开失败问题问题现象:双机热备环境下,CAS2.
0版本上未启用模板存储(没有挂载任何非本地模板存储),从CAS2.
0升级到E0306H02之前的CAS3.
0版本后,启用模板存储服务(挂载非本地模板存储);或者CAS2.
0版本上启用了模板存储(挂载了非本地模板存储),从CAS2.
0升级到E0306H02之前的CAS3.
0版本后,禁用模板存储服务(删除所有非本地模板存储),这两种场景下的操作会导致CAS管理界面打开失败.
问题产生条件:双机热备环境下,从CAS2.
0升级到E0306H02之前的CAS3.
0版本后,启用或禁用模板存储服务.
规避措施:双机热备环境下,CAS2.
0版本上未启用模板存储(没有挂载任何非本地模板存储),从CAS2.
0升级到E0306H02之后,再启用模板存储服务(挂载非本地模板存储);或者CAS2.
0版本上启用了模板存储(挂载了非本地模板存储),从CAS2.
0升级到E0306H02之后,再禁用模板存储服务(删除所有非本地模板存储).
1015.
安装或升级CAS出现/etc/default/grub选择的问题问题现象:安装或升级CAS时,出现选择/etc/default/grub选项.
Anewversionofconfigurationfile/etc/default/grubisavailable,buttheversioninstalledcurrentlyhasbeenlocallymodified.
1.
installthepackagemaintainer'sversion2.
keepthelocalversioncurrentlyinstalled3.
Showthedifferencesbetweentheversions4.
Showaside-by-sidedifferencebetweentheversions5.
showa3-waydifferencebetweenavailableversions6.
doa3-waymergebetweenavailableversions(experimental)7.
startanewshelltoexaminethesituation问题产生条件:升级CAS版本概率性出现.
规避措施:请选择方式2.
Keepthelocalversioncurrentlyinstalled.
8解决问题列表8.
1E0509H01版本解决问题列表8.
1.
1虚拟机状态异常问题问题现象:主机下的所有虚拟机图标状态显示蓝色问号,左键点击其中一台虚拟机能变成正常的运行状态,进入其属性页面或者退出登录,虚拟机状态又会变成蓝色问号.

问题产生条件:主机CPU越多,流量越多情况下概率出现.
8.
1.
2UNIC-NIC-10GE-2P-520F-B2网卡无法识别问题问题现象:在安装CAS完成后,UNIC-NIC-10GE-2P-520F-B2网卡无法识别.
问题产生条件:存在UNIC-NIC-10GE-2P-520F-B2网卡的服务器.
8.
1.
3信息泄露漏洞CNVD-2017-32023问题问题现象:在线操作员查询页面存在信息泄露的漏洞,漏洞是由CAS云计算平台的会话中cookie来控制,且cookie内容仅为会话ID所致,攻击者登录系统后,通过修改cookie可获取超级管理员权限.
问题产生条件:通过修改cookie获取超级管理员权限.
8.
1.
4页面跳转问题问题现象:当CAS访问页面My97DatePicker.
html时,页面会跳转到http://www.
my97.
net/地址.
问题产生条件:访问http://CVM_IP:8080/cas/js/lib/My97DatePicker/My97DatePicker.
htm,CVM_IP是用户的管理平台IP地址.
118.
2E0509版本解决问题列表8.
2.
1Broadcom部分网卡不支持SR-IOV功能问题问题现象:直接部署CAS5.
0版本,Broadcom部分网卡无法在CVM界面开启SR-IOV功能.
例如:网卡型号BroadcomLimitedBCM57840NetXtremeII10/20-GigabitEthernet.
问题产生条件:使用厂商设备ID为14e4:16a2的Broadcom网卡,例如:BCM57840网卡.
8.
2.
2虚拟机镜像被删除问题问题现象:不同主机下的虚拟机共用同一存储(置零或延迟置零模式),迁移其中一台主机下虚拟机的存储到另一存储池中,导致另一主机下的虚拟机镜像被删除,处于deleted状态.
问题产生条件:迁移不同主机下虚拟机共用的存储.
8.
2.
3删除模板报未知错误问题问题现象:在CAS管理平台上增加多个模板,使得模板有多页,翻到最后一页,删除这一页的所有模板,删除最后一个模板成功后,报未知错误提示.
问题产生条件:模板有超过一页时,删除第二页最后一个模板.
8.
2.
4Nova插件挂载磁盘不兼容问题问题现象:升级到CAS5.
0版本后,在CloudOS上新建磁盘(新建过程没有选项来指定是virtio的还是iscas的).
该磁盘在CAS界面上虚拟机概述页面无法显示,在虚拟机操作系统上也无法识别.
如果在修改虚拟机页面上删除该磁盘,提示"设备不存在"错误.
问题产生条件:在CAS3.
0之前创建的虚拟机,在CAS升级到5.
0之后,给虚拟机挂载磁盘.

8.
3C0508版本解决问题列表8.
3.
1日志分区占满问题问题现象:访问记录的日志文件没有定时清理,系统长时间运行导致日志分区被占满.

问题产生条件:系统长时间运行.
8.
3.
2File安全漏洞问题问题现象:File安全漏洞CVE-2014-3538、CVE-2012-1571、CVE-2013-7345、CVE-2014-2270、CVE-2014-1943、CVE-2014-8116、CVE-2014-8117.
问题产生条件:File安全漏洞问题.
8.
3.
3TLS1.
2握手漏洞问题问题现象:TLS1.
2握手漏洞CVE-2015-7575.
问题产生条件:TLS1.
2安全漏洞问题.
8.
3.
4OpenSSL安全漏洞问题问题现象:OpenSSL安全漏洞CVE-2017-3737、CVE-2017-3738.
12问题产生条件:OpenSSL安全漏洞问题.
8.
3.
5Emulex10GbE网卡故障问题问题现象:多台CVK报网卡故障告警(6个网卡其中一个,其余网卡均正常),告警的那个网卡EmulexCorporationOneConnect10GbNIC(be3)(rev01)在CAS页面上处于不活动的状态.
问题产生条件:HPE服务器使用hp-be2netV11.
1.
183.
21及以前驱动.
8.
4E0506版本解决问题列表8.
4.
1Tomcat性能下降问题问题现象:在主机过多的情况下,长时间运行的Tomcat会出现内存占用过多的问题,导致FULLGC,使Tomcat性能下降.
问题产生条件:多主机情况下,Tomcat长时间运行使其占用较多内存.
8.
4.
2虚拟机未故障迁移问题问题现象:对虚拟机做外部快照,使得虚拟机镜像文件发生变更,由1级变成4级.
在主机故障后,虚拟机进行故障迁移时,使用旧的虚拟机定义文件去部署虚拟机,导致启动虚拟机报错.

问题产生条件:虚拟机做外部快照使其镜像文件变更.
8.
4.
3VMware上安装CAS问题问题现象:CAS(CVM/CIC)安装在VMware的虚拟机上,在虚拟机未开启串口情况下,可部署成功.
问题产生条件:CAS(CVM/CIC)安装在VMware系统上.
8.
4.
4虚拟机无法迁移问题问题现象:通过OpenStack接口下发虚拟机,新增网卡后,无法迁移.
问题产生条件:虚拟机通过OpenStack接口下发后,新增网卡,执行迁移操作.
8.
4.
5Web页面应用渗透漏洞问题问题现象:Web页面做应用渗透测试,发现高中危问题:任意文件下载(高危)、命令注入(高危)、全盘目录浏览(中危)、敏感信息泄露(中危)、OPTIONS方法(低危).
问题产生条件:对Web页面最应用渗透测试.
8.
4.
6数据库连接错误问题问题现象:双机热备的环境,执行CAS版本升级操作.
升级过程中报数据库连接错误,升级完成后,界面无法启动虚拟机.
问题产生条件:双机热备的环境,执行CAS版本升级操作.
8.
4.
7虚拟机异常状态问题问题现象:主机触发Fence后,但是没有执行后续的Fence退出流程,集群阻塞,也没有触发后续的HA的迁移动作.
13问题产生条件:不同HOSTSET之间分配的LUN号不同,将HOSTSET1中的主机移至另一个HOSTSET2.
8.
4.
8导出虚拟机OVF模板超时问题问题现象:导出虚拟机OVF模板的过程中,由于操作员闲置时长超时界面退出,导致模板下载失败.
问题产生条件:导出虚拟机的OVF模板过程中,界面超时退出.
8.
4.
9ApacheTomcat安全漏洞问题问题现象:ApacheTomcat安全绕过漏洞(CVE-2017-5664).
问题产生条件:ApacheTomcat安全漏洞.
8.
5E0503版本解决问题列表8.
5.
1主机Fence重启问题问题现象:管理网异常,导致主机重启.
问题产生条件:多个虚拟机交换机配置ACL策略.
8.
5.
2动态聚合UP慢问题问题现象:动态聚合时,物理交换机端口DOWN之后重新UP,发现LACP很快协商成功,但是OpenvSwitch端的聚合端口状态还是Disable状态(ovs-appctlbond/show).
问题产生条件:动态聚合,物理交换机端口DOWN、UP操作.
8.
5.
3WEB页面应用渗透漏洞问题问题现象:WEB页面做应用渗透测试,发现高中危问题:任意文件下载(高危)、命令注入(高危)、全盘目录浏览(中危)、敏感信息泄露(中危)、OPTIONS方法(低危).
问题产生条件:对WEB页面最应用渗透测试.
8.
5.
4性能监控无数据问题问题现象:CVM双机热备服务切换后,主机虚拟机的性能监控无显示数据.
问题产生条件:双机热备服务切换.
8.
5.
5集群阻塞问题问题现象:管理网频繁闪断导致集群阻塞.
问题产生条件:管理网频繁闪断.
8.
5.
6主机加入集群失败问题问题现象:启用集群HA功能,有些主机加入集群失败.
问题产生条件:启用集群HA.
148.
5.
7两节点零存储环境配置仲裁IP无法启动的问题问题现象:零存储服务无法正常启动.
问题产生条件:两节点零存储环境,配置了仲裁IP.
8.
5.
8零存储和S1020V共用时零存储无法注册License的问题问题现象:零存储无法注册License.
问题产生提交:节点上同时部署了零存储和S1020V.
8.
5.
9零存储做数据平衡导致根分区满的问题问题现象:零存储内部平衡数据,系统的根分区空间耗尽.
问题产生条件:零存储平衡数据但是无法完成时.
8.
5.
10零存储Admin进程退出引发CAS集群重启的问题问题现象:Admin进程退出,120s内无法选举出新的Admin进程.
问题产生条件:零存储Admin进程退出8.
5.
11零存储进程异常退出问题问题现象:零存储进程退出.
问题产生条件:非常小概率出现零存储进程退出.
8.
6E0502版本解决问题列表8.
6.
1BFA驱动异常问题问题现象:存储链路异常导致BFA驱动异常,导致主机重启.
问题产生条件:在存储链路异常情况下,使用3.
2.
23.
0版本BFA驱动的服务器.
8.
6.
2CPU热添加导致虚拟机挂死问题问题现象:启动RedHat6.
4、6.
5、6.
6版本或CentOS6.
4、6.
5、6.
6版本的虚拟机,在运行超过5小时后,进行CPU热添加,发现虚拟机高概率挂死.
问题产生条件:安装RedHat6.
4、6.
5、6.
6版本或CentOS6.
4、6.
5、6.
6版本的虚拟机,运行超过5小时.
8.
6.
3Nova插件无法获取存储池列表问题问题现象:CloudOS通过Nova插件查询CAS的存储池列表,CloudOS无法获取查询结果.
问题产生条件:CloudOS通过Nova插件查询CAS的存储池列表.
8.
6.
4虚拟机拉取组播流量异常问题问题现象:虚拟机在某些情况下退出组播组,且无法重新加入.
问题产生条件:虚拟机持续(每隔5秒内)发送IGMPReport报文.
158.
7E0501版本解决问题列表版本首次发布.
9技术支持用户支持邮箱:service@h3c.
com技术支持热线电话:400-810-0504(手机、固话均可拨打)网址:http://www.
h3c.
com.
cn10相关资料10.
1相关资料清单H3CCAS云计算管理平台安装手册H3CCAS云计算管理平台快速入门10.
2资料获取方法您可以通过H3C网站(www.
h3c.
com.
cn)获取最新的产品资料:(1)请访问网址:http://www.
h3c.
com.
cn/Technical_Documents,或单击主页的[服务支持/文档中心];(2)选择产品类别和产品型号,即可查询和下载与该产品相关的手册.
11版本升级操作指导11.
1版本升级介绍11.
1.
1CAS1.
0升级到CAS5.
0介绍H3CCAS产品包含了1.
0版本、2.
0版本、3.
0版本和5.
0版本,如果现场的CAS版本还是CAS1.
0版本,则无法直接升级到CAS5.
0的最新版本,首先需要手工修改管理虚拟交换机的名称,然后依次完成过渡版本到目标版本的升级.
1.
手工修改管理虚拟交换机的名称因为CAS2.
0版本中管理虚拟交换机的名称固定为"vswitch0",而CAS1.
0版本则没有这个要求,所以在升级前,需要确保管理虚拟交换机的名称为"vswitch0",否则无法正常升级.

手工修改管理虚拟交换机名称的方法如下:步骤1正常关闭虚拟机,并在集群中删除主机.
步骤2用显示器键盘连接主机或者iLO方式登录主机,执行命令vi/etc/network/interfaces,将管理虚拟交换机的名称修改为"vswitch0".
16步骤3依次执行以下命令,如下的管理虚拟交换机以绑定的eth2为例,如果现场的管理虚拟交换机绑定的物理接口为eth1,那么下面的将eth2修改为eth1,第2条命令中的vswitch2修改为vswitch1:ovs-vsctldel-porteth2ovs-vsctldel-brvswitch2ovs-vsctladd-brvswitch0ovs-vsctladd-portvswitch0eth2步骤4通过ovs-vsctlshow命令查看修改结果,确保修改成功后,将主机重新加入到集群.
步骤5通过tail–f/var/log/syslog命令查看是否存在异常,确保主机成功加入集群后,重启服务器,完成管理虚拟交换机名称的修改.
2.
过渡版本到目标版本的升级举例:若当前版本为CAS-F0120版本,则需要按照如下顺序升级CAS-E0509H01版本:CAS-F0120->CAS-F0123H06->CAS-E0203H01->reboot(重启机器)->CAS-E0306->reboot(重启机器)->CAS-E0509->CAS-E0509H01->reboot(重启机器)升级步骤和要求如下:步骤1从当前CAS1.
0版本(CAS-F0123H06之前的版本)升级到CAS-F0123H06版本,升级前需要关闭HA,并暂停业务(正常关闭虚拟机和暂停共享文件系统),升级完成后不重启每台主机.
步骤2从CAS-F0123H06版本升级到CAS-E0203H01版本,升级前需要关闭HA,并暂停业务(正常关闭虚拟机和暂停共享文件系统),升级完成后必须重启每台主机.
步骤3从CAS-E0203H01版本升级到过渡版本CAS-E0306,升级前需要关闭HA,并暂停业务(正常关闭虚拟机和暂停共享文件系统),升级完成后必须重启每台主机.
步骤4从CAS-E0306版本升级到目标基础版本CAS-E0509,升级前需要关闭HA,并暂停业务(正常关闭虚拟机和暂停共享文件系统),升级完成后不重启每台主机;若CAS与亚信杀毒包配合使用时,亚信防病毒从CAS-E0306升级到CAS-E0509必须重启每台主机.
步骤5从CAS-E0509版本升级到目标版本CAS-E0509H01,升级完成后必须重启每台主机;如果是双机热备环境,升级完成后,必须先重启每台主机,然后手动启动热备服务.

11.
1.
2CAS2.
0升级到CAS5.
0介绍如果现场的CAS版本是CAS2.
0版本,需要先升级到过渡版本CAS-E0306,升级完成后需要重启每台主机,然后再直接升级到目标基础版本CAS-E0509,再升级到目标版本CAS-E0509H01,升级完成后需要重启每台主机.
举例:若当前版本为CAS-E0222版本,则需要按照如下顺序升级CAS-E0509H01版本:CAS-E0222->CAS-E0306->reboot(重启机器)->CAS-E0509->CAS-E0509H01->reboot(重启机器)升级步骤和要求如下:步骤1从CAS-E0222版本升级到过渡版本CAS-E0306,升级前需要关闭HA,并暂停业务(正常关闭虚拟机和暂停共享文件系统),升级完成后必须重启每台主机.
步骤2从CAS-E0306版本升级到目标基础版本CAS-E0509,升级前需要关闭HA,并暂停业务(正常关闭虚拟机和暂停共享文件系统)升级完CAS-E0509后,不重启每台主机;若CAS与亚信杀毒包配合使用时,亚信防病毒从CAS-E0306升级到CAS-E0509必须重启每台主机.
17步骤3从CAS-E0509版本升级到目标版本CAS-E0509H01,升级前需要关闭HA,并暂停业务(正常关闭虚拟机和暂停共享文件系统),如果是双机热备环境,升级完成后,必须先重启每台主机,然后手动启动热备服务.
11.
1.
3CAS3.
0升级到CAS5.
0介绍如果现场的CAS版本是CAS3.
0版本,低于CAS-E0306版本的环境必须先升级到CAS-E0306版本,升级完成后需要重启每台主机,然后再升级到目标基础版本CAS-E0509,再升级到目标版本CAS-E0509H01,升级完成后需要重启每台主机.
举例:若当前版本为CAS-E0303版本,则需要按照如下顺序升级CAS-E0509H01版本:CAS-E0303->CAS-E0306->reboot(重启机器)->CAS-E0509->CAS-E0509H01->reboot(重启机器)升级步骤和要求如下:步骤1从CAS-E0303升级到过渡版本CAS-E0306,升级前需要关闭HA,并暂停业务(正常关闭虚拟机和暂停共享文件系统),升级完成后必须重启每台主机.
步骤2从CAS-E0306版本升级到目标基础版本CAS-E0509,升级前需要关闭HA,并暂停业务(正常关闭虚拟机和暂停共享文件系统),升级完CAS-E0509后,不重启每台主机;若CAS与亚信杀毒包配合使用时,亚信防病毒从CAS-E0306升级到CAS-E0509必须重启每台主机.
步骤3从CAS-E0509版本升级到目标版本CAS-E0509H01,升级前需要关闭HA,并暂停业务(正常关闭虚拟机和暂停共享文件系统),如果是双机热备环境,升级完成后,必须先重启每台主机,然后手动启动热备服务.
11.
1.
4重要版本介绍CAS发布的版本有些支持在线升级,有些版本则需要暂停业务(关闭虚拟机、暂停共享存储池)升级并或者需要重启主机生效.
升级过程前首先需要获取待升级局点的CAS版本信息,然后结合下表的版本介绍制定升级方案.
序号目标版本内核版本是否需要重启主机暂停业务或重启主机说明1CAS-E05014.
1.
35是所有模块均刷新.
2CAS-E05024.
1.
35是所有模块均刷新.
3CAS-E05034.
1.
35是所有模块均刷新.
4CAS-E05064.
1.
35是所有模块均刷新.
5CAS-C05084.
1.
35是所有模块均刷新.
6CAS-E05094.
1.
35是所有模块均刷新.
7CAS-E0509H014.
1.
35是内核模块OCFS2、OpenvSwitch有更新,升级完成后,需要重启机器生效.
1811.
1.
5CAStools介绍1.
版本号:5.
0.
9.
12.
H3CCAStools安装手册从CAS3.
0版本开始,CAStools版本号规则变更为四位,由点号分隔:前三位表示CAS版本号,后一位表示CAS补丁号.
若CAS发布版本时,CAStools版本未更新,则CAStools版本号不变;下次若有变更,则直接跳到对应的CAS版本号.
11.
1.
6升级环境介绍H3CCAS产品主要包含了如下三种场景的版本升级:(1)非零存储环境下的CAS版本升级:指在未配置零存储及双机热备的环境中升级CAS版本.
(2)CVM双机热备环境下的CAS版本升级:指在未配置零存储但配置了CVM双机热备的环境中升级CAS版本.
(3)零存储环境下的CAS版本升级:指在配置了零存储的环境中升级CAS版本.
11.
1.
7升级方式介绍H3CCAS产品主要包含了如下四种方式的版本升级:(1)串行升级CVK:在CVM上执行".
/upgrade.
sh"开始升级版本.
先串行升级每台CVK(不包括CVM所在CVK),然后升级CVM,执行完成后,CVM及所管理的CVK均升级完成.
(2)单独升级CVK:将升级包拷贝到CVK上,解压后,在升级目录执行".
/upgrade.
sh--force-cvk"或".
/upgrade.
sh-fcvk"开始升级版本.
执行完成后,当前CVK升级完成.
(3)并行升级CVK:在CVM上执行".
/upgrade.
sh-pcvks"开始升级版本.
先并行升级所有CVK(不包括CVM所在CVK),然后升级CVM,执行完成后,CVM及所管理的CVK均升级完成.
该升级方式自E0218H06版本开始支持.
(4)单独升级CVM:在CVM上执行".
/upgrade.
sh–fcvm"开始升级版本.
执行完成后,CVM所在的机器升级完成,如果是双机热备CVM,则两台CVM均升级完成.
11.
1.
8升级脚本参数介绍查看升级脚本帮助信息,如下:root@#.
/upgrade.
sh-hUsage:.
/upgrade.
sh[option]option:[|-pcvks|precheck|postcheck|copy|-fcvm|-fcvk|--force-cvk|restore|mysql]Description:19.
/upgrade.
sh:SeriallyupgradeallCVKsmanagedbyCVM.
ExecuteupgradeonCVM,CIC,orSSVhost.
.
/upgrade.
sh-pcvks:ParallellyupgradeallCVKsmanagedbyCVM.
ExecuteupgradeonCVM,CIC,orSSVhost.
.
/upgrade.
shprecheck:Pre-checkCASupgradeenvironment.
.
/upgrade.
shpostcheck:Post-checkCASupgradeenvironment.
.
/upgrade.
shcopy:Pre-copypackagetoallhosts.
.
/upgrade.
sh-fcvm:ForciblyupgradetheCVKofCVMself.
ExecuteupgradeonCVMhost.
.
/upgrade.
sh-fcvk:ForciblyupgradetheCVK.
ExecuteupgradeonCVKhost.
.
/upgrade.
sh--force-cvk:ForciblyupgradetheCVK.
ExecuteupgradeonCVKhost.
.
/upgrade.
shrestore:JustrestorethelastversionfileofCASenvironment.
.
/upgrade.
shmysql:Upgrademysqldatabase.
(1)预检查参数:.
/upgrade.
shprecheck,检查当前环境是否满足升级条件.
预检查如下几个方面:1)版本文件及版本信息是否满足升级.
2)升级包、CVM包、CVK包是否存在,不存在则报错.
3)MySql服务是否正常运行,如果没有运行,则尝试启动,启动失败则报错.
4)HA服务是否启用,如果启用,则提示先禁用.
5)获取管理平台的组件:CIC/CVM/SSV.
6)Tomcat服务是否正常运行,如果没有运行,则尝试启动,启动失败则报错.
7)获取CAS安全模式:保密还是非保密.
8)获取CVM的模式:单机环境还是双机热备环境,并检查双机热备是否正常.
9)获取CVM管理的所有主机列表.
10)检查所有主机列表的网络是否正常,根分区剩余空间不少于4G大小,/vms分区剩余空间不少于4G大小,apt-getcheck检查,检查不通过,则提示报错.
以上检查必须通过之后,预检查才通过,也才能进行下一步的升级操作.
若有检查不通过项,控制台可看到错误,错误解决之后才能继续升级操作.
(2)验收检查参数:.
/upgrade.
shpostcheck,升级结束后检查升级环境是否存在错误.
如下图所示,升级完成后,会做postcheck检查,检查结果存放在/var/log/upgrade/postcheck-report_timestamp.
txt文件中,timestamp是时间戳.
20升级完成之后,验证报告必须要查看一下,里面记录了升级环境是否有错误[ERROR]或者是否有告警[WARN],告警项会涉及一些操作,必须仔细阅读.
比如:重启机器的告警,修改共享存储参数为61的告警.
已添加的验收检查内容包括:1)前台WAR包大小检查2)前台数据库字段是否缺失检查3)CAStools版本号及文件数目检查4)驱动文件正确性检查5)Apt-getcheck检查6)内核升级检查7)OCFS2心跳参数检查8)版本信息检查(3)预拷贝参数:.
/upgrade.
shcopy,将CVK包预先拷贝到其他CVK主机上/root分区下.
预拷贝之前会做precheck检查,检查通过之后才允许拷贝版本.
(4)单独升级CVM参数:.
/upgrade.
sh-fcvm,用于单独升级虚拟机化管理平台(包含CVM、CIC、SSV),升级包括前台包组件及CVM所在的CVK后台组件.
主要应用场景:不断业务,逐台升级CVK后,最后升级CVM所在的CVK,不再将升级包拷贝到其他CVK上比较CVK的版本号,直接升级本CVM所在的CVK即可.
双机热备环境下,主CVM、备CVM都会升级.
(5)升级数据库参数:.
/upgrade.
shmysql,单独升级前台数据库.
该命令属于异常情况下的补救措施.
应用场景:升级完成之后,由于mysql服务异常导致前台组件数据库未升级,请先将数据库修复之后,mysql服务启动运行正常,然后再执行该命令单独升级数据库.
(6)回退版本信息21参数:.
/upgrade.
shrestore,只回退上一个版本信息.
该操作是异常情况下,方便一键回退所有主机的版本信息,重复升级使用,属于异常操作,需谨慎使用,不能反复使用.

回退之前会做precheck检查,检查通过之后才允许回退版本信息.
回退的内容有:1)CAS版本文件/etc/cas_cvk-version,将/etc/last-cvk-version还原为/etc/cas_cvk-version或/etc/h3c-cas_cvk-version2)Tomcat变化的版本,即:从CAS2.
0升级到CAS3.
0、CAS5.
0,tomcat从tomcat6升级到tomcat8,此时也会回退tomcat6的权限,把/etc/init.
d/tomcat6权限改回可执行,把/etc/init.
d/tomcat8权限去掉可执行,将tomcat6服务启动.

主要应用场景:升级过程中断,或其他异常情况下,需要重复升级版本.
双机热备环境需要先确保双机热备服务正常,MySql服务运行正常后,才能执行.
/upgrade.
shrestore.
11.
1.
9升级日志文件介绍升级日志及升级相关信息统一存放在/var/log/upgrade/目录下面.
包括内容有:1)升级历史版本信息文件:cas_upgrade_history.
txt,该文件记录了历史升级版本的时间、CAS版本信息.
2)CVM升级日志文件:cvm-upgrade_timestamp.
log,timestamp是时间戳,该文件记录了在CVM上执行升级时,打印到控制台上的所有日志信息.
3)CVK升级日志文件:cvk-CVKIP_upgrade_timestamp.
log,CVKIP是CVK的IP地址,timestamp是时间戳,该文件记录了在CVK上执行升级时的所有日志信息.
4)Postcheck报告文件:postcheck-report_timestamp.
txt,timestamp是时间戳,该文件记录了升级完成后,对升级环境的验收检查,详细记录了环境中的错误信息.
11.
1.
10升级注意事项(1)升级包(压缩包)解压出来的升级包目录,不可直接拷贝到其他CVM或CVK上使用,请务必将升级包(压缩包)完整拷贝到其他CVM或CVK上,解压使用.
(2)在业务可中断的场景下,必须中断业务升级,如果要求业务不中断,请联系CAS研发.
(3)若从3.
13.
6内核升级到4.
1内核,即:从E0222前的版本要升级到E0225及之后的大版本,必须要页面禁用HA,否则,升级完成后HA功能不可用.
(4)从E0222前的版本要升级到E0225及之后的大版本,升级到mysql-server-5.
5包时会出现6~7分钟无任何输出的情况,是由于Mysql正在生成配置文件'/etc/init/mysql.
conf',此时不能中断升级,需耐心等待配置文件完成,升级操作会继续执行.
(5)若从E0209H11之前的版本升级到4.
1内核版本,旧内核存在小概率主机不能重启,主机下某台虚拟机存储路径丢失的问题,该问题出现后,只能通过重启服务器解决.
因此,这种升级场景推荐暂停业务升级.
22(6)在线升级到E0306和E0306H01版本时,如果集群中存在共享存储池,O2CB参数O2CB_HEARTBEAT_THRESHOLD不是61,升级脚本会提示自动修改该参数为61.
若是单机环境,此时必须先执行脚本ocfs2_update_o2cb_params.
sh将O2CB参数O2CB_HEARTBEAT_THRESHOLD改回31,然后一台一台重启主机后,再执行脚本ocfs2_update_o2cb_params.
sh修改O2CB参数O2CB_HEARTBEAT_THRESHOLD为61.
若是双机热备环境,必须先一台一台重启主机,使能双机热备后,再执行脚本ocfs2_update_o2cb_params.
sh将O2CB参数O2CB_HEARTBEAT_THRESHOLD改回31,待共享存储池挂载成功后,再执行脚本ocfs2_update_o2cb_params.
sh修改O2CB参数O2CB_HEARTBEAT_THRESHOLD为61.
(7)如果之前版本携带了零存储,那么需要先升级到E0306H11版本过渡,然后再升级到E0501及之后的CAS5.
0版本.
(8)如果有用CVK模拟的NFSServer,需要先删除以CVK模拟NFSServer的NFS类型存储池再升级E0501及之后的CAS5.
0版本.
(9)CAS与亚信杀毒包配合使用时,需要先卸载低版本亚信杀毒包,再升级CAS版本,再安装对应高版本亚信杀毒包,安装新版本亚信杀毒包后,需要在DSM里把CAS计算域删除再添加.
(10)CAS与亚信杀毒包配合使用时,亚信防病毒从E0306升级到E0509必须重启.
11.
1.
11双机热备环境升级注意事项(1)在CVM双机热备环境下包括了Master和Slave状态的CVM主机,当升级Master状态的CVM主机时,Slave状态的CVM主机也会被同步升级.
因此,需要将版本升级包上传到Master状态的CVM主机,并且在Master状态的CVM主机执行升级操作.
(2)如采用SSH,请连接CVM的Master状态的主机的管理IP地址进行升级,不要用热备提供的虚拟IP地址,否则可能会有不可知错误.
(3)双机热备环境,凡内核进行了大版本升级的版本,如:E0225、E0306版本(其他版本内核升级情况参考11.
1.
3重要版本介绍),在内核大版本升级过程中,热备服务为了升级需要,会自动关闭.

升级后双机热备服务不会自动启动,待主机重启新内核生效后,必须手动在命令行中执行cvm_resource_start.
sh来启动热备服务.
(4)双机热备环境,从小于E0225的版本升级到CAS3.
0E0303版本的补丁版本,在升级到CAS3.
0E0303大版本时,必须先重启主机,待手动启动热备服务器后,再升级补丁版本,否则,补丁版本无法完成升级.
如:从E0218升级到E0303H03,升级完E0303后,必须先重启每台主机,手动启动热备服务,然后再升级到目标版本E0303H03,升级完成后,再次重启每台主机.
E0306之后的版本升级可不遵循此原则,升级脚本中会自动检查双机热备是否启动,如果没有启动,会自动拉起后,再执行升级.
11.
2版本升级操作步骤H3CCAS系统主要包括了CVK、CVM、CIC和SSV组件.
每个主机默认安装CVK组件,而CVM、CIC和SSV组件则需要授权信息选择安装;CVM、CIC和SSV组件既可以安装在同一台主机也可以安装在不同的主机;如果CVM、CIC和SSV组件安装在同一台主机上,则升级CVM管理平台时,会自动同步升级CIC和SSV组件.
同时,CVM管理的所有CVK主机也将被同步升级.
23若CVM、CIC和SSV组件安装在不同主机上,则升级CVM管理平台时只会同步升级CVM管理的所有CVK主机.
而安装CIC和SSV组件主机则需要单独升级.
严禁把装有CVM、CIC和SSV组件的CVK再作为CVM使用,否则可能有不可知的错误.
11.
2.
1升级前准备1.
查看CAS系统状态H3CCAS系统在进行版本升级的过程中,有可能需要执行虚拟机关闭、共享文件系统暂停,重启主机等操作.
为了确保升级完成后CAS系统可以快速恢复到升级前的状态,需要在执行版本升级操作前检查CAS系统的运行状态.
检查CAS系统运行状态的内容主要包括:集群状态:高可靠性(HA)、动态资源调度(DRS)和电源智能管理(DPM)主机状态:主机的运行状态(必须是正常运行)、虚拟交换机状态、存储池状态虚拟机状态:记录下虚拟机的运行状态,未正常运行的虚拟机需要和客户确认2.
备份虚拟机升级版本前,建议对虚拟机进行备份.
单击导航树中"////"菜单项,进入虚拟机概要信息页面,点击按钮,弹出"立即备份"对话框.
建议将虚拟机备份到远端服务器.
3.
备份重要业务数据H3CCAS虚拟化环境中运行了客户虚拟机,在升级CAS系统的过程中有可能需要关闭虚拟机或者重启主机,一定程度上会影响到客户业务系统的正常运行.
为了确保业务系统数据的可靠性,建议备份应用业务数据,比如使用Oracle自带的exp功能备份数据库数据.
4.
检查待升级主机与所连存储服务器的连接状态在升级CAS系统时,尤其是涉及到内核版本升级时,为了确保正常升级、业务系统数据可靠,建议升级前确认待升级主机与存储服务器的连接状态正常.
245.
准备版本升级包(1)获取升级包从H3C公司网站下载版本升级包软件.
版本软件在H3C公司网站的存放路径为:"///".
版本软件下载URL:http://www.
h3c.
com.
cn/Service/Software_Download/H3Cloud/Catalog/Cloud_Virtualization/CAS_CVM(2)上传升级包使用SSH工具将CAS升级包"CAS-E0509H01-Upgrade.
tar.
gz"上传至CVM主机的"/root"目录下.
上传完成后,通过SSH工具登录CVM后台,确认版本升级包已经成功上传至"/root"目录.
通过MD5值,检查上传至CVM主机上的版本升级包与本地的版本升级包大小是否一致.
(3)解压缩版本升级包在CVM主机的"/root"目录,解压缩版本升级包,命令如下:tar-xzfCAS-E0509H01-Upgrade.
tar.
gz版本升级包解压缩完成后,会生成"upgrade.
e0509h01"目录.
11.
2.
2暂停业务在制作升级方案时需要根据11.
1版本升级介绍的内容确认从待升级版本到目标版本是否需要暂停业务.
1.
关闭虚拟机禁止通过CAS平台中虚拟机的按钮执行关机操作,原因为强制关闭电源有可能损坏虚拟机的文件系统,导致业务异常.
建议通过虚拟机操作系统内部的关机按钮执行正常关机操作,或者通过CAS平台中虚拟机的按钮执行正常关机操作.
2.
页面关闭HA版本升级必须要页面关闭HA,并且先执行页面关闭HA,再执行暂停存储池操作.
升级完成后,重启主机之前,HA将不可用.
在"/"的对话框中去掉"启用HA",并点击按钮.
3.
暂停存储池在"//"的页面,点击按钮来暂停共享存储.
注意:各个CVK主机下的共享存储池都需要暂停.
11.
2.
3升级预检查25请使用SSH工具进行升级操作,不建议使用iLO口进行升级操作,禁止使用CAS的Xconsole的tty1界面进行升级(可以通过Xconsole的tty2界面升级,在Xconsole的tty1界面下按+即可切换至tty2界面);升级过程中CVM、CIC、SSV系统无法正常访问.
通过SSH客户端,登录CVM主机后台,进入版本升级包目录,然后执行预检查命令".
/upgrade.
shprecheck"开始预检查升级环境.
检查当前环境是否满足升级条件.
预检查如下几个方面:1)版本文件及版本信息是否满足升级.
2)升级包、CVM包、CVK包是否存在,不存在则报错.
3)MySql服务是否正常运行,如果没有运行,则尝试启动,启动失败则报错.
4)HA服务是否启用,如果启用,则提示先禁用.
5)获取管理平台的组件:CIC/CVM/SSV.
6)Tomcat服务是否正常运行,如果没有运行,则尝试启动,启动失败则报错.
7)获取CAS安全模式:保密还是非保密.
8)获取CVM的模式:单机环境还是双机热备环境,并检查双机热备是否正常.
9)获取CVM管理的所有主机列表.
10)检查所有主机列表的网络是否正常,根分区剩余空间不少于4G大小,/vms分区剩余空间不少于4G大小,apt-getcheck检查,检查不通过,则提示报错.
26以上检查必须通过之后,预检查才通过,也才能进行下一步的升级操作.
若有检查不通过项,控制台可看到错误,错误解决之后,再次执行预检查通过,才能进行升级操作.