执行software-packages stage --iso的时候提示错误如下
The CD drive does not have a valid patch ISO or has an unsupported version

通过SSH登录VCSA控制台，进入shell模式下执行

rm /dev/sr0; sleep 5; mknod /dev/sr0 b 11 0; chown root:cdrom /dev/sr0; chmod 660 /dev/sr0

重新挂载ISO后执行software-packages stage --iso即可。

- 阅读剩余部分 -

vCenter 在运行 ESX 8.0 U3 或更高版本的受支持主机的集群上部署嵌入式 vCLS。对于使用早期版本的主机集群，vCenter 将部署外部 vCLS。vCenter 清单允许多个版本的 ESX 共存，在滚动 ESX 升级期间会发生这种情况。对于混合版本的集群，只要集群中的任何可用主机支持嵌入式 vCLS，vCenter 就会使用嵌入式 vCLS。这将创建一个点，当主机在升级到受支持的版本后退出维护模式时，将集群从外部 vCLS 升级到嵌入式 vCLS。vCenter 会等待第一个嵌入式 vCLS 虚拟机可用，然后停用外部 vCLS 并销毁这些虚拟机，从而无缝进行该升级。此外，如果所有受支持的主机都变得不可用，并且仅保留不受支持的主机，vCenter 可以恢复为外部 vCLS。但是，由于此步骤基于主机变得不可用，因此可能会导致嵌入式 vCLS 卸载和外部 vCLS 部署之间发生 DRS 不可用。

vCLS 使用代理虚拟机维护集群服务的运行状况。将主机添加到集群时，将创建 vCLS 代理虚拟机（vCLS 虚拟机）。在外部 vCLS 中，每个 vSphere 集群中最多需要运行 3 个 vCLS 虚拟机，并在集群内进行分发。此外，也可在仅包含一个或两个主机的集群上激活外部 vCLS。在这些集群中，vCLS 虚拟机数量分别是 1 和 2。在嵌入式 vCLS 中，每个 vSphere 集群中最多需要运行两个 vCLS 虚拟机。

https://docs.vmware.com/cn/VMware-vSphere/8.0/vsphere-resource-management/GUID-96BD6016-4BE7-4B1C-8269-568D1555B08C.html

将补丁文件上传/下载到设备

加载并运行补丁

patch load FM-S7700_V200R022SPH220.pat all run

加载Web网管文件
执行命令system-view，进入系统视图。
执行命令http server load { file-name | default }，加载Web网页文件。

验证补丁是否安装成功

display patch-information

Hello!

As you probably know, F5 closed Moscow office in 2022, and I no longer work for F5 since then. Still, we’ve reached an agreement that I will maintain my role in nginx development as a volunteer. And for almost two years I was working on improving nginx and making it better for everyone, for free.

Unfortunately, some new non-technical management at F5 recently decided that they know better how to run open source projects. In particular, they decided to interfere with security policy nginx uses for years, ignoring both the policy and developers’ position.

That’s quite understandable: they own the project, and can do anything with it, including doing marketing-motivated actions, ignoring developers position and community. Still, this contradicts our agreement.
And, more importantly, I no longer able to control which changes are made in nginx within F5, and no longer see nginx as a free and open source project developed and maintained for the public good.

As such, starting from today, I will no longer participate in nginx development as run by F5. Instead, I’m starting an alternative project, which is going to be run by developers, and not corporate entities:

http://freenginx.org/

The goal is to keep nginx development free from arbitrary corporate actions. Help and contributions are welcome. Hope it will be beneficial for everyone.

--
Maxim Dounin
http://freenginx.org/

  1. 1
  2. 2
  3. 3
  4. 4
  5. ...
  6. 57