Quick Tip – Changing default port for HTTP Reverse Proxy on both vCenter Server & ESXi

本文介绍如何在vCenter Server、VCSA及ESXi主机上修改默认的HTTP(80)和HTTPS(443)端口,以自定义HTTP反向代理服务。更新内容包括vSphere 6.7中对自定义端口的支持,以及在不同平台上配置文件的位置和重启服务的方法。

If you decide to use a custom port for the HTTP Reverse Proxy (rhttpproxy) on vCenter Server which uses port 80 (HTTP) and 443 (HTTPS) by default, you should also apply the same change on all ESXi hosts being managed by that vCenter Server for proper functionality. The configuration files for the rhttpproxy has since changed from the early days of vSphere 5.x and in vSphere 6.x, there are now different.

UPDATE (04/27/18) - With release of vSphere 6.7, VMware now officially supports customizing the Reverse HTTP(s) Ports on the VCSA. Below is a screenshot using the VCSA Installer UI and this can also be customized in the JSON configuration file using the VCSA CLI Installer for automation purposes.

Below are the instructions for modifying the default ports for rhttproxy service for both Windows vCenter Server, vCenter Server Appliance (VCSA) and ESXi host.

Note: If you change the default ports of your vCenter Server, you will need to ensure that all VMware/3rd Party products that communicate with vCenter Server are also modified.

vCenter Server for Windows

On Windows, you will need to modify C:\ProgramData\VMware\vCenterServer\cfg\vmware-rhttpproxy\config.xml and look for the following lines to change either the HTTP and/or HTTPs ports:

<httpPort>80</httpPort>
<httpsPort>443</httpsPort>

Once you have saved the changes, you will need to restart the VMware HTTP Reverse Proxy service using Windows Services Manager.

vCenter Server Appliance (VCSA)

On the VCSA, you will need to modify /etc/vmware-rhttpproxy/config.xml and look for the following lines to change either the HTTP and/or HTTPs ports:

<httpPort>80</httpPort>
<httpsPort>443</httpsPort>

Once you have saved the changes, you will need to restart the rhttpproxy service by running the following command:

/etc/init.d/rhttpproxy restart

ESXi

On ESXi, you will need to modify /etc/vmware/rhttpproxy/config.xml and look for the following lines to change either the HTTP and/or HTTPs ports:

<httpPort>80</httpPort>
<httpsPort>443</httpsPort>

Once you have saved the changes, you will need to restart the rhttpproxy service by running the following command:

/etc/init.d/rhttpproxy restart

 

内容概要:本文详细介绍了在没有DNS解析的情况下,各版本VMware vCenter Server Appliance(VCSA) 使用静态IP进行部署的方法及其注意事项。针对不同的版本(如vSphere 7.0.3、7.0.1、6.7、6.5及更早版本),提供了解决部署过程中可能遇到的问题的具体步骤,以及对已知缺陷或错误提示的说明。例如,针对某些特定版本,在第一阶段部署时FQDN设置应填写VCSA的静态IP而不是空白或者无效DNS值,并强调了一旦完成初始配置后需等待人工干预才能继续到下一步;同时对于7.0U2以后的部分版本还需手动编辑host文件添加映射关系以便跳过系统内部尝试获取域名解析这一环节。此外文章还指出部分较新的vSphere 7.x版本如果遇到长时间卡在某进度的情况可能是因无法解析主机名所造成,建议提前检查确认网络参数是否配置恰当。最后提醒了6.5/6.0的老版本并不强制验证DNS配置,部署相对更加简单灵活。 适用人群:从事IT基础设施运维的技术人员,尤其是那些负责搭建、维护基于VMware平台的企业级私有云环境的专业人士。 使用场景及目标:在企业数据中心内部网络中当DNS服务不可用或其他原因导致无法使用标准命名方式进行组件间通讯识别的状况下,确保能正确高效地建立管理虚拟化资源所需的控制节点&mdash;&mdash;即vCenter实例。这不仅有助于快速恢复业务连续性而且可以在测试实验室环境中作为临时性的解决方案来满足各种实验探索的需求。另外通过学习这份材料可以让相关工作者熟悉不同年代产品之间特性差别从而积累宝贵的实际操作经验。 其他说明:值得注意的是,尽管文中列举了所有提及的解决方案都有效规避掉了DNS缺失带来的麻烦,但在实际生产环境尽可能保持良好完善的基础设施建设依然是推荐做法之一。而本文所提供的非传统手段仅限应急响应期间短期采取,长期来看仍有必要构建稳定的DNS服务体系保障日常运作平稳有序。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值