大网数据广告活动
服务器运维问答

Cobbler and PXE

· 52CE 我爱测

I have successfully installed a Cobbler server in virtualized Centos in a ESXi, so I can provide automated installation for a small bare-metal cluster I need to set up. There is a black boxed DHCP and DNS set up in my company I c…

问题原文

原帖链接 · Navarro · CC BY-SA 3.0

I have successfully installed a Cobbler server in virtualized Centos in a ESXi, so I can provide automated installation for a small bare-metal cluster I need to set up.

There is a black boxed DHCP and DNS set up in my company I can't manage nor check.

When I set in a sample box I have to boot over NIC with PXE, I can't properly select the IP of the Cobbler server, it tries to get a DHCPD address and then fails.

I am sure there is an elephant in the room I am currently unable to see, could anyone enlighten me on this topic? Should I create a small closed network just to be in charge of Cobbler's DNS/DHCP modules?

已采纳解答

原帖链接 · Sven · CC BY-SA 3.0

You don't necessarily need to run your own DHCP/DNS server with a cobbler installation, but in order to boot properly via PXE, the DHCP server must send additional attributes to the clients (at least next-server and filename which contain the hostname of the TFTP server and the filename to load from it).

If you can't have these attributes added to the DHCP config for the new cluster members, you would indeed need to setup your own VLAN with DHCP server, but talk to your companies networking team before starting.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-01-02)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。