I have kickstart installations booting just fine using
esx ks=http://157.194.210.29/esx/VDInn.cfg ip=10.10.10n.nn netmask=255.255.248.0 gateway=10.10.104.1 ksdevice=eth0
is there a vlan option that I can add to that line? Like vlan=3020 or something at the very end after ksdevice=
I ask because I want to set the switch ports for the server to no specific vlan and let the server do the vlan tagging.
Hello,
That will work for when you reboot your ESX server, however it will not work for a kickstart. There is no ksvlan (kickstart vlan) option available to the kickstart code. I wish there was, but kickstart uses a straight Linux kernel and to move VLANs into the kernel you need special drivers which do not exist during the kickstart.
Consider installation to only support EST (External Switch Tagging) and you play it safe. If straight Linux does not support it, then ESX installations will not. Later you can move things to a VLAN quite easily.
Best regards,
Edward
Add this to your VDInn.cfg
--addvmportgroup=0 --vlanid=100
i.e.
\# Network install type
network --device eth0 --bootproto static --ip 10.42.10.10 --netmask 255.255.255.0 --gateway 10.42.10.1 --nameserver 10.42.10.100 --hostname server1.co.uk --addvmportgroup=0 --vlanid=100
Message was edited by:
Mooihoek
Right, I will put that in there, but if the switchport for the NIC is not in a particular vlan, then the installer can't reach the webserver to download the config. Does kickstart not support vlan tagging? If so, fine, I will set the switchport to the vlan and then remove it later.
Hello,
That will work for when you reboot your ESX server, however it will not work for a kickstart. There is no ksvlan (kickstart vlan) option available to the kickstart code. I wish there was, but kickstart uses a straight Linux kernel and to move VLANs into the kernel you need special drivers which do not exist during the kickstart.
Consider installation to only support EST (External Switch Tagging) and you play it safe. If straight Linux does not support it, then ESX installations will not. Later you can move things to a VLAN quite easily.
Best regards,
Edward
Okay, thanks. I want to do vlan tagging so I can have different vlans for the service console, vmotion, and my guest VMs.
Back to the original question...
esx ks=http://157.194.210.29/esx/VDInn.cfg ip=10.10.10n.nn netmask=255.255.248.0 gateway=10.10.104.1 ksdevice=eth0
is there a vlan option that I can add to that line? Like vlan=3020
I have two vlans trunked and tag to the port this server is connected to. I can not get to the kickstart file because I can not get on the network unless I disable trunking and tagging. Is there a vlan option that I can add to that line?
Thanks,
Bob
Texiwill explained it well, there is no option to do this. What you can do is use Native VLAN tagging to tag untagged packets with a specific VLAN, that will get your installation rolling while still providing you with the ability to have multiple VLANs on your service console or management network port.