In this example we're going to build a NetBoot image from a bootable drive. The first step is to build a bootable drive! I don't recommend using your regular boot drive. Instead, install OS X on another drive or partition. I'm not going to give you a step-by-step about how to do this. Hey everyone, I'm trying to sort out setting up NetBoot (NetBoot/SUS Appliance) in a Windows and Cisco environment that is already using PXE booting. My understanding is the two can co-exist, but will need some help from DHCP. I see a lot of reference to IP Helpers, but mostly in conversations regarding NetBooting across subnets. I also know some people use DHCP Options. What I haven't been able to sort out is, if I need both and if I need to use DHCP Options, which ones. I know it may not be that simple regarding which options, but it sounds like the IP Helper address is pretty straightforward. Anyway, hoping someone can share how they've approached/accomplished this. I keep hunting for info on this and finding threads like this that say it works fine, but no info on HOW to set it up. Can anyone provide that info? In other words, what is the DHCP option for netboot? PXE boot uses option 66 and 67 (server and file) or the equivalent (Bluecat Proteus uses Next Server and File Name service options instead of those DHCP client options. Anyone know what client options or service options netboot needs to have set? It obviously can't be the same options as PXE as you can only set one value for those, and the seemingly great mystery is what are the magic options for netboot? But what is the option you use in DHCP for the netboot server IP? PXE server IP is under option 66, but I've still never found anyone who can say what the option is for Netboot. To put another way, I'm not sure I understand your reply because the helper IPs in the network hardware point to the DHCP server. The DHCP server then has the client or service options that point to PXE, and presumably Netboot. We have PXE working fine, and can't find how to add Netboot to this environment. Thanks for any assistance with the specifics you can provide! To the OP regarding DHCP options: First some clarification on what makes up a NetBoot Server. Can you provide more details on your setup and exactly what you are trying to do? It sounds like you have a netboot server and a mac os x client device on different subnets. I'll assume that your netboot server is on the same subnet as your other network servers like DHCP server, Mac Server, Windows Server etc etc etc There will be a switch or router connecting the two subnets, this will have a place usually called ip_helper that allows you to place an IP address of a server that will accept broadcast traffic from the other subnet. So in this example, your IP helper should contain the IP address of both your DHCP server and your netboot server. Thats pretty much it. Theres not a lot of magic to it. Curious how did you test the.nbi files 'locally'? How did you create the nbi? There is a switch directly connected to a core router connecting the two subnets here is the IP helper added in: core1#show run int vl65 Building configuration. Current configuration: 294 bytes! Interface Vlan65 description Casper Test Workstations ip address 10.xx.65.254 255.255.255.0 ip helper-address 10.xx.195.28 ip helper-address 10.xx.207.28 ip helper-address 10.xx.195.145 ip helper-address 10.xx.195.240 no ip redirects no ip unreachables no ip proxy-arp end I have crossed out some of the IP addresses for security, 10.xx.65.0 is the vlan i'm connecting from and 10.xx.195.240 is my netboot server. When I say I tested it locally I meant I spun up a local VM environment with VMware fusion on one of my workstations and was able to netboot between hosts(they were on the same subnet tho) I used AutoCasperNBI to build my nbi. Heh thats my docker container;) Looks like your NBI is not setup correctly. How did you make it? ![]() It looks like the nbimageinfo.plist is not setup corerctly, See where is saying skipping 'no description' it should probably have a description. Make sure you don't have any spaces in the name of your NBI also You'll need to pay attention to the nbimageinfo.plist specifically around the enabled/disabled arrays This is what i do on my nbimageinfo.plist i basically remove all the machines from the disabled array, and add only the really old machines i dont support.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2019
Categories |