Gain in-depth knowledge for passing your exam with Exam-Labs 1z0-821: Oracle Solaris 11 System Administration certification video training course. The most trusted and reliable name for studying and passing with VCE files which include Oracle 1z0-821 practice test questions and answers, study guide and exam practice test questions. Unlike any other 1z0-821: Oracle Solaris 11 System Administration video training course for your certification exam.

Installing Oracle Solaris 11

4. Interactive Installer pt. 2

Now we're actually going to take a look at using the interactive installer. For this part of the course, we're going to do a demonstration on an installation from the Oracle Solaris Eleven live CD. This was the same one that we looked at earlier when I showed you the quick tour of Solaris Eleven. So let's get started and see how to install from a live CD. All right, we're here in Solaris 11, in the Oracle VirtualBox version of it. And what we're going to do is install Oracle from this live CD. So the first thing we want to do is go ahead and double click on the icon here. And one thing you should know is that some of the things that we'll talk about take a little bit of time. So I may occasionally stop the recording process when I know that a step is going to take several minutes. And we won't skip any parts, but it will be a little bit time-condensed for you, so we don't bore you to death by watching a blank screen or the system. Don't do much of anything for a little while. So the first thing we see is the installer screen. and this is very easy to do. We see a welcome message, and it's going to tell us to look at the release notes. We're going to click next. Now it tells us what kind of drive we have. And I have a virtual drive installed on the machine, and it's a 16-gig drive. And that's the kind of minimum that Solaris alone asks for when it creates a virtual machine. I'm going to go ahead and do a simple install. We're just going to use the entire disk. It tells us that the recommended size is seven gigabytes and the minimum is five gigabytes. That's important to know for your hardware requirements. During a later presentation, we'll look at partitioning the disc, and you can do it during the installation, or you can do it later on if you leave unpartitioned space available for you. Now you can look and see what kind of partition types we can use—unused, extended, and so forth. We're going to go ahead and use the whole disc at this point. Let's click Next at any time. You can quit the installer by pressing the quit button or get help, obviously. So here we will set the time. And I'm just going to pick a region arbitrarily. I'm going to pick New York. I'll pick Eastern Time. And we'll leave the clock where it is and go on to click Next. And this is where we provide it with username and login name information. So I'm just going to put my own information in here, and we'll call it Bobby. And then it gives you the opportunity to enter your password in.You always want to use a complex password, bythe way, in any system you use or administer,we can change the computer name if we want. I'm going to change it to BTC. For the time being, we're going to click Next. And now we have some settings that we can review. And the settings that we can review are the disc size and partition, the software we're going to install, obviously the time zone, the default language, language support, and the user account information. And one thing you'll notice here is that it creates a user account as I specified, and it automatically sets the root password to the same as the user account. This is not necessarily a good thing for an initial install. So as soon as you get this installed, you want to change this. It says the hostname is VTC. Now the solaris live CD, it's actualusername and password that it uses. For the username, it's Jack, and the password is Jack for the root account. For the live CD, it's root and solaris, all lower case. Now as soon as you change this, that changes the root password, obviously for an install on the hard drive. So let's go ahead and click Install. And this is where it can get a little boring. This is where you can go get a cup of coffee and so on, as well as do other things. So what we may do is go ahead and pause this and actually bring you back to it when it starts doing some things that are of interest. So this can take some time to install the software, to let it go ahead and copy files, and so forth. So it's going to do a few things here, nothing of real consequence that you interact with. You've pretty much done most of the interacting you're going to do. This is a very simple installation process. It's very easy to use. It doesn't require a lot. You actually do a lot of your configuration after the system is installed. Now we've come to the conclusion of the Solaris Eleven installer process. Now we did time lapse through some of the boring stuff where the system was copying files and so forth, but there was nothing where the user really needed to interact with the system. When you install it on your own for the first time, you'll kind of see that it's pretty much a good place to go get a cup of coffee or go do something. The total installation can sometimes last up to an hour. Now that we've come to the last screen here for the interactive installer, it tells us that the installation is complete and we can look at the installation log for more information. Let's just click that really quickly and kind of look at what it contains. Some of this may not make sense right now, but there's a lot of information on things like performing disc maintenance, doing partitioning, and so forth, installing device drivers, setting up configuration parameters, and so forth. So if you have any issues during this installation, you can always look here on the install log. Let's go ahead and close this. And right now, the next step really is to reboot the system. And when we reboot, we should come into a fully installed Solaris 11 system still in VirtualBox but installed on the virtual hard drive. So at this point we'll go ahead and do that, and then in the later session we'll do a text install.

5. Interactive Installer pt. 3

Now that we've discussed the interactive installer in detail and we've also looked at a live CD installation, Now we're going to do a demonstration of an installation using the text installer CD itself. Now, normally you would use this method of installation when you're installing a Solaris server or when you have a low-end graphics card or maybe not enough system memory for the live CD installer to run. Now, one thing I'll mention is that we are going to abbreviate this installation a little bit simply because sometimes it can take a great deal of time. So I'm going to skip the boot sequence and kind of start you out where the installer portion starts. Trust me, we'll have plenty of time to review the Solaris 11 boot sequence a little bit later on in the course. For right now, we'll pickup where the installation starts. Let's go ahead and take a look at it. All right, we're on the installation screen. Again, this is using the text installer, and it's already booted. We've already selected a keyboard and a language, and then we got to the screen. So from this screen, we can do different things. Obviously, we want to install Oracle Solaris, but we can also choose to install additional drivers. We can go to a shell, we can go to the terminal, we can set it to the terminal type, and we can reboot the system if we like. Let's do a simple install and go ahead and see what we get. We're going to enter one. And again, this can take a little bit of time. It really depends on several things. It depends upon the speed of your processor, how much memory you have, the hardware on your computer, and so forth. Okay, we get our initial screen here, and it's going to tell us where the install log is. And again, it reminds us that it can install on Spark or X86 platforms. One thing about this installer is that it typically continues. The inner key doesn't do too much. So watch for the bottom of the screen. It will tell you what your options are. So we're going to go ahead and hit F2 for Continue. It's going to look at the discs on the system itself, and it's going to tell us what the recommended and minimum sizes are. Now it's telling us that we have a 16-gig set of drives there, and it's going to suggest a partition table for us. Now we can go ahead and accept that, obviously, or we can go ahead and later on decide to change that. So I'm going to accept what is offered there by using f two. And again, it suggests to us that we use either the whole disc or partition the disk. Let's go ahead and go with the whole disc for right now. Again, for two. Now, three will get us back, six will get us help, and nine will stop the process. One thing you need to know is that you have to be focused on a particular option in order for the other two to continue to accept that option. So we're going to go ahead and type in a name for the box. And again, as I said, you have to have something selected in order to continue. So we're going to go ahead and select the automatically configure the connection option. Now we could go ahead and enter that manually. I'll show you how to do that a little bit later when we talk about configuring the network. Let's go ahead and hit Continue. And this is where we get our time zone information from. It begins by categorising it by region. So we'll go to the Americas. as I'm recording from North America. and then you get to select the country from the region. And unfortunately, it's not very intuitive to type the word, so it won't get you down to the United States or that area. So we have to kind of scroll down a little bit. I'm going to head up there again, and then I'm going to just select the time zone. I'm going to go with the Eastern time zone. going to hit two. And you can select your time zone when you're installing, and we can pick the time when we want to install. It obviously uses the 24 hour format and tries to go by the system clock date that you have, and we're going to leave that time and date there. Now, unlike the live CD, you actually get to select a root password here, whereas on the live CD, whatever user account you create gets that password also. So let's go ahead and give it a goodroot password, which you must confirm. And then we'll create an account, and then, two, don't hit enter, and it will summarise the installation for you, all the options you selected. And really, this is a lot like the GUI version. It just looks a little bit differently. So we have the F2 install option here, which I'm going to go ahead and take. And this is probably where I'm going to time lapse a little bit because it can do this for a little while. It will prepare for the installation, and then we'll transfer files over. And that can take some time depending upon how fast your CD-ROM is, how the hardware on the machine is configured, and so forth. So we're going to time lapse a little bit, and when we come back, you'll see that this is completed. All right, now we've completed the installation, and of course we need to reboot in order to make this boot in our new installation. And if we want to review the installation log, it's located at the location shown on the screen for the system volatile install log. And after rebooting, you can look at it in the DM system logs installation log, and you'll want to look at that to troubleshoot anything or just to make sure that the installation went well. So let's go ahead and reboot. And that concludes our discussion on using the interactive text installer CD.

6. Verify the Installation

Now that we've installed Solaris 11, we may want to verify that we had a good installation. Now if you see anything or any issues causing the system not to boot or anything like that, then you obviously don't have a good installation, and we'll talk about troubleshooting in a moment. There are several ways to verify, though, that you have a good installation. The first one is, well, it works, and that's the main thing you want to do: make sure that everything's working. You're looking for a good boot and no error messages. You're looking for things that are supposed to be working—applications that are working, network or Internet connectivity, and things of that nature. There are several things you can do to verify this. First of all, you can verify that you have Internet or network connectivity. And this is assuming that you configure your network to connect to the Internet or to the network that you're using. You can also verify your disc partitioning to make sure everything went according to plan. You can also look at the installation log to view any issues that may have happened during installation. But typically, you will have seen some error messages that floated by while you were installing. If there's going to be anything in the installation log, still, it's a good idea to look. Another thing you can do is look at system messages, and I'll show you how to do this in a moment. But typically you just run the Dmessage command from the command prompt. Let's go ahead and go into Solaris Eleven and take a look at the installation log and at the system messages. Now that we're in Solaris 11, there are a couple of different ways we can look at the installation log. There's an application already installed called GEdit that will help you do this. And if you're used to using Notepad or something similar in Windows, G Edit is basically the same thing. You can also use the terminal, which we'll do here. In a second, you can open up the G Edit text editor from Accessories and then navigate to where the log is stored. Now let's go ahead and open, and we'll want to look in the file system. We'll also want to look under VAR, which is where a lot of your system logs are stored, by the way. And we'll want to look under SADM, kind of short for system administrator, if you will, under System and under Logs. And there we have the install log. Let's open that up, and we can see the install log here on the screen. And I've kind of changed the background colour just so you can see it a little bit better. There's a lot of information here, and it might be best to look at it in the terminal prompt. But you can see where it was preparing for installation—where it transferred files. And we saw this on the screen; if you've installed it, you've seen that before, and you can go down and just kind of see if there were any issues with this, and there really weren't during this installation. So let's go ahead and close this. Let's look at it in the terminal. Let's make our terminal a little bit bigger here, and we're going to go into VAR system logs, where we see the install log there.Let's catch the install log, and if you've done any kind of Linux or Unix at the command prompt or at the shell prompt, then you know what cat is. It basically sends a text file to the screen, and to prevent it from just scrolling on, we're going to pipe it into Less and we'll see the same information we saw before. You can now go one at a time by pressing the space bar or the Enter key. Spacebar to go one page at a time, and you can see the installation log there. You may have to go through it a little bit to find any issues that you may have had, and keep in mind I've changed the font. The screen size and so forth are just for this video, so you can see a little bit better, but you may be able to see it better when you actually install and look at it on your own. in your own terminal. The other thing you may want to do is send the message rather than using the D message command, look at the message or at system messages; this is actually simple; just type in D message, and of course it kind of scrolls by, so you may want to do this and pipe it into a less. That way, you get it a little bit at a time, and you can hit the space bar to go one page at a time, and you'll see if there are any issues or warnings, and there are a few here that we see but nothing major that may have contributed to a bad installation. We haven't seen anything yet, so there may be nothing to see, but there's a good place to look if you do have issues, and again, you kind of have to know what you're looking for and kind of match it up with the areas that you're getting, but D-Bus is a very valuable tool to use to try to track down issues. Okay, we verified the installation by looking at the installation log in and the system messages; there are no issues there, and we can also confirm that everything works properly. We can look at applications and so forth, and that will verify that the system installed as it was supposed to. If you can log in and use the system, there have typically been no issues. There may have been a minor issue or two, but nothing major. So it looks like our system is installed. Very good. So we verified it, and everything is good to go. In another session, we'll talk about troubleshooting when things don't go very well.

7. Troubleshooting Installation

Now that we've installed Solaris Eleven, we've also looked at the installation. We've verified that it was installed properly and everything works. Now what happens when it doesn't work? Well, fortunately, Solaris 11 is very, very robust, very easy to use, easy to install, and actually does a very good job of detecting hardware and resolving issues on its own. However, things can go wrong occasionally. But to be honest, there's not too much that can go wrong. There are some hardware planning issues that may cause problems, and there are some other issues as well. Let's take a look at some of those. First of all, the obvious is what we want to check. Let's look at the media we're trying to install from.In other words, when you've downloaded the ISO and burned it to a CDROM, you want to make sure that it's a good CD and that it's not scratched or scuffed up. You also want to make sure that it's been recorded in a format that your CDROM reader can read and detect. So, if you've got a good medium, tested it, and it works fine, and a good CD-ROM on your system, that shouldn't be a problem. Now, if you're installing from across the network—maybe you've booted from the text installer—and you're relying on network installation files, then there could be issues if you don't have the correct network server settings. What you want to make sure is that you've got the correct server, possibly the server name and the correct IP address, and that the server is configured to serve out the installation files properly. Typically, you will create that server andits files with the automated installer. And that's, again, a different subject for a different time. That's not part of the objectives we're talking about at this time. In any event, that's what you would use to make that network server work and do what you want it to do: the automated installer. So there may be issues on the network server side as well. On the client side, the one you're trying to install, make sure that you have good network connectivity and that you're connecting to the right server. Now, one of the bigger things that can go wrong during an installation is the hardware. There can be hardware issues. And actually, this is where planning comes into play. Often you may think that any old hardware will work, so you try to install it, and maybe it seems to go well until it suddenly stops, errors out, throws an error message, or something like that. What you may want to do is check your hardware compatibility before you start. On the Oracle website, there is also a list of hardware compatibility. You also may want to check to make sure your hardware is functioning properly. If you have, say, a hard disc array, perhaps a scuzzyarray, make sure that it works before you try to install it. Make sure your network card is working. Make sure you have the right and proper amount of RAM. Make sure your video is working. Sometimes people may try to install on an older machine because Solaris doesn't require an awful lot and maybe the piece of hardware is compatible with Solaris, but it just doesn't work. So check that if there are issues. Make sure your system meets the minimum requirements, and we talked about what those were when we discussed the installers. In the end, you're probably going to have to replace any faulty hardware that you may find or any incompatible hardware, or you may wind up installing on a different system. One of the things that we discussed earlier with Verifying the installation is actually looking at the installation log, and we're not going to look at that again, but you can locate that in the Varsadmsystemlogsinstall log. That's assuming that your system does actually install to the point where you can get to the log. If you don't get that far, then obviously the log is going to be incomplete and not do you any good anyway. So you'll have to troubleshoot error messages as you get them. There may be error messages with RAM, CPU, hard disc space, or the hard disc array. One of the common mistakes that a lot of people make, and yours truly is one of those people, is trying to install Solaris 11 on a 32-bit processor. Solaris Eleven is a 64-bit operating system and, as such, requires a 64-bit processor. So don't make the mistake of popping it into any old 32-bit machine and thinking that you can install it. It typically will not work, and you'll get some really funny error messages that may not lead you to the right conclusion initially. So the moral of this story is that you may also want to look on the Oracle site and try to troubleshoot any error messages you see with them. They actually have a very comprehensive troubleshooting source on their site under Solaris 11, and this will help you out a lot. The other thing you can do, assuming you can boot into the system, is check your system messages. You'd typically type in Dmesg at a command prompt, assuming you can get to one, and it will give you all the system messages that have occurred since boot. And what you'll see is any errors there, which you may have to track down several of because there could be errors that corrected themselves and errors that did not. So you'll have to look through your D message list to see what's out there and try to trace that back to the issue that caused the installation problem in the first place. So it can be a little bit difficult, but typically it's going to be some kind of hardware issue that's going to be your main issue, more likely faulty media or a faulty network connection. So, again, troubleshooting is not that difficult with Solar Eleven because there's not a lot that can go wrong. Usually you can narrow it down to one of those three things we just discussed.

8. Access Open Boot PROM

Now we've talked about Solaris Eleven booting to a small degree, and really we've focused on X86 platforms, and as part of this installation process, we're going to talk about accessing the open boot prompt, or OBP, which has been around for a little while, at least since Solaris Ten at least.And what we have is what is usually used on the Spark platform. We're just going to touch the OBP a little bit. We're going to talk about starting up and shutting down Solaris 11 both on X86 and Spark platforms a bit later. So this is just basically telling you what open boot prompt" or OBP really is. Now the PROM, which stands for programmable read-only memory That's the system firmware, and we really want to open the boot PROM on the Spark. Now, as we've seen on X86 platforms, grab. You haven't seen that yet, but you probably will before this course is over with. You'll be familiar with it. Right now we're going to talk about the OVP just a little bit to kind of familiarise you with it. Now the OBP is basically used to access the boot device on a Spark platform and transfer the boot archive to the system memory. Now this process is called bootstrapping, and you've probably heard of it before. Even PCs use bootstrapping a little bit differently, but they use bootstrapping to load the executable software into memory that boots the computer. Now there are a couple of different commands that you can use with the open boot prompt, or OBP. And again, don't get wrapped around the axle with these just yet. We're going to talk about starting up and shutting down the system later on in the course. The boot command is one of those, and you can use this with parameters. For example, you can say boot net at the prompt, and it will boot into a network type of boot. In other words, it will go out and find a DHCP server and possibly boot from a network image. There are some other commands that you can use as well. The E PROM utility is used again on a Solaris box to set the PROM parameters. It can set network parameters, network boot parameters, and the boot device itself, and so forth. Monitor is another command that we use to access the prompt; we'll cover it a little bit later as well. And there are also other commands that we can use that really aren't part of the E-Prom Monitor, but they access the Prom in certain ways. For example, Banner can tell you what version of the PROM you're running, or in other words, what version of firmware you're running. There are several other commands and options available at the prompt for configuring boot devices. Look at Scuzzy devices, get device IDs, and things like that, and they all access the boot PROM firmware, the open boot PROM. So we'll talk about these a little bit as we go through the course. And you'll probably learn a lot more when we talk about starting the system up and shutting it down. This will be discussed over the course of several sessions. So this is just an introduction to the open boot prompt, what it is, and kind of what it does for you. And really, we see this on a Solaris Eleven box that's installed on a Spark platform, not so much on an X86 platform. And you'll notice that as we progress through the course, the majority of the discussion will most likely be X86-focused because that's where the community is heading. That's where most of these servers are being installed. Now, Spark is a great platform. It's really fast, but it's not really compatible with a lot of other things—really just Solaris 11 and Solaris 10 and a few other versions of Solaris—and it's really not compatible with any other operating system. And the tendency is to go buy something and install it that can run different things and is more compatible. So the Tenancy is becoming to buy X86 systems and install a wide variety of things on them, of which Solaris 11 is obviously one. So you'll see the course slightly slanted toward the X86 platform, but we will discuss Spark issues and architectures as we go through it. So stay tuned, and you'll get some more information on Spark as we get through the course. You.

Pay a fraction of the cost to study with Exam-Labs 1z0-821: Oracle Solaris 11 System Administration certification video training course. Passing the certification exams have never been easier. With the complete self-paced exam prep solution including 1z0-821: Oracle Solaris 11 System Administration certification video training course, practice test questions and answers, exam practice test questions and study guide, you have nothing to worry about for your next certification exam.

Hide