If the JUNOS installer doesn't like your disk layout, it seems it'll tweak it to meet its needs. On my fresh install it's sitting at just under 700M used. The /var disklabel needs to be big enough to hold future software update bundles, core dumps, log files, etc. I told fdisk to use the entire disk (option A) and laid out my disklabels like so: I ran through the FreeBSD installation, choosing the "standard" installation.
Once the VM was created I connected its CD/DVD drive to the FreeBSD ISO I downloaded and powered on the VM. If you install something older than 4.11 you will not have any network interfaces that are usable by Olive. This is the chipset that is emulated by VMware (at least under ESXi 4.1) when choosing the e1000 network adapter type. Through some experimentation and reading of the em(4) man page I found that FreeBSD 4.11 is the only 4.x release that supports the Intel 82545EM chipset. My final Olive install is sitting around 1G used. I used the default size of 8G which turns out to be more than enough.
The e1000 adapter type causes VMware to present an Intel based chip to the VM which JUNOS is capable of using.Not needed for Olive, but needed to install FreeBSD.You will need a valid Juniper support contract to download the jinstall bundle. I will not share copies of any Juniper software so please don't ask. A copy of the jinstall 10.4R1 package (specifically, I used the M/MX/T series install package).FreeBSD 4.11 mini-iso (I specifically needed 4.11 more on this below).I had these items on-hand before starting: The installation breaks down into four major steps: Update June 3 2011: Mention that it's ESXi that I'm working with. I also wanted to document how to get Olive up inside VMware ESXi since I hadn't actually done that before. I wanted to take another stab at it and document how to get a working Olive installation using the latest JUNOS code. It's been a long time since I've taken a run at getting Olive up and working.
0 kommentar(er)
