Lesson 2: Install and Configure - Installing Storage Foundation and Accessing SF Interfac...

Page 1 of 2

LESSON 2: INSTALL AND CONFIGURE - INSTALLING STORAGE FOUNDATION AND ACCESSING SF INTERFACES DEMO
PRINT DOCUMENT

BOB LUCAS: Hello and welcome to Labs and Demos for the Storage Foundation 5.1 for UNIX web-based training course. I'm going to

take you through some of the labs and demos in this class that support the lecture sessions that we covered in your video training.
And I'm actually going to be working from the same .pdf-based printed document that you should have received when you took the
instructor-led Storage Foundation 5.1 for UNIX training class. So you have printed instructions of everything that I'm going to go over
in the Demos and Labs today. I've selected certain sections that I think are key to help you understand the product better and to help
you understand how the labs support the lecture sessions that were covered in both the video training and the instructor-led training.
And I'd like to start with this Lab Number 2, which supports Lesson 2 of the training. And we're going to start with the installer.
That's a good place to start. We'll install the product, and I'll take you through some of the steps that we cover for the common
platform installer scripts, the CPI scripts. Now bear with me if I have to jump around a little bit, if I make any typos. I'm not the
greatest typer in the world, but hopefully it won't be too bad. So we're going to start with the installer in the directory where Storage
Foundation 5.1 is located. This is a Solaris-10 machine, SPARC-based, so we're going to follow the Solaris specific instructions in the
lab. Okay and here's your menu for the installer. We're going to install a product. Notice how you can also do a pre-installation check
if you want to. We already did that, and we checked out okay so we'll skip that for now. Install Storage Foundation product. I have to
say yes to this question here if I want to go on. I may also refer back to this lab document every once in a while to make sure I'm
leading you down the right path here. So we're going to install all Storage Foundation packages, and that's number three. And my
system name is Train11, so I'm just going to hit Return. And I want to show you something else that I can do with the installer.
Basically any time I want, I can just do a Control-C and that interrupts it, and I do get a log or what little of a log there is because I
didn't do very much. I will get something saved at that location. But I'm going to start over for two reasons. One was the reason I
just described. I wanted to show you that I can just interrupt it and start it over again, and notice how when I start it over again it'll
discover that I tried to do an installation and had a problem. Do I want to resume this process, I'm going to say no. I want to start a
new installation. Because the other reason I've started over here is I want to show you I can install more than one system at the
same time. So I'm going to do all those same answers, and when the system prompts me for the systems, I'm going to give it
Train11 space Train12. Now Train11 and 12 are 2 SAN connected machines on the same LAN. So I'm going to install the product on
both the boxes at the same time. And this time I'm not going to interrupt it. I'm just going to let it go. So it's checking some of these
things right here, giving you any messages about errors that may occur. Hopefully we won't find any. And then eventually it's going
to ask if I want to do keyless licensing. Let's keep an eye out for that. Okay so we should be back in right now. So at this point we're
up to 93%. And now it's installed what looks like all the packages. It's putting the libraries and scripts on there, checking to see if I
have any license keys for Storage Foundation. And I don't so I'm going to go ahead and pick the default, which is two, keyless
license. And I'm going to pick the default here, which is Enterprise. I don't want to enable Volume Replicator. It's going to register
the license. Notice how the lab has me check my profile in the bin directory. Here's one of the paths I mentioned in the video training
right there. You need a link there to etc/vx bin. We have all that on our systems, so I'm not going to worry about that for this lab.
Now it says, do you want to send the information about the installation to Symantec. I'm going to say no. In a minute here I'm going
to take you over to the log files so you can see what's been logged. So now it wants me to reboot because the VXSF package add
should have added a line to my /etc/system file. There it is in there, VXFS start and VXFS end. And because of that I'll need to reboot
both boxes to make that take effect. Now bear in mind this is a test box, not a production box, so I'm going to do a reboot and that's
fine for my test box. Goodbye. Okay so we've rebooted both systems. We've installed the product successfully, and the installer has
created logs for us to look at. So you can see the directory I'm in right there. I'll do an LS and several log files were created as a
result. And notice how I can also see some logs from Train12 here and Train11, which is nice to have. And so I can look at, for
example, a response file that was created as a result of my answers to the prompt questions in the install. And you can see how I
answered each prompt, keyless licensing, enterprise license, configure, install, accept the EULA, Storage Foundation 5.1. And this
becomes a very useful file that I can use elsewhere for other installations of similar or identical boxes. Something nice to have. Here's
a screen shot of vxlicrep more. You can just see that in your lab book here. If you have key-based licenses on here it will show those
keys and the enablement and all the component products associated with that key. We've X'ed out the keys for security purposes
there, but your key should show up. So now the product is installed, and I should be able to do commands like package info,
(inaudible) VRTSvxvm and VRTSvxfs, and there they are. And any time you want to see exactly what version of one our product
packages you have, you do the pkginfo-l for long format, and then you get something like that. Okay and we can also see the version
of the product we have by doing the pkginfo-l of the package, and this is what we get when we do that. And you can see 5.1 is on
here, so we're looking good. So now I'm going to set up the VEA, Veritas Enterprise Administrator, and I want to prove to you that
the server was installed but the GUI client piece of the VEA was not installed. See how we have OB on there, but we don't have OB
GUI. So we've downloaded OB GUI on this machine that we're running. And all we have to do in the lab here is the same thing you
did in your instructor-led class labs is you ran /opt/VRTS/bin, and I think it was vxsvcctrl, activate. And that starts the server. You do
SVCS -l, system VxSvc. Okay and see it's running. That's the default, it's online, it's logging to that log file right there. Okay I can do
ps -ef pipe to grep vxsvc. And it is running because in Solaris all I needed to do was that activate command, but on Linux I'll have to
do the start, which was this command right there. But Solaris does both activate and start, so I'm good to go. So now I have to go
over to this /student/sf/vea_gui. Okay and in here, I have my OB GUI packages, which is the thing that we didn't install as part of the
installation. So it looks like the package is already there. Actually, it's there but I have to uncompress it. So before I do this package
add command right there, I'm going to have to copy one of these into a place where I can get to it. (inaudible) with cd/tmp,
(inaudible). Okay now we can do pkgadd-d . and we'll say yes to that, yes, yes, yes, yes, yes. And there goes the OB GUI. So we'll
kick off VEA, we're going to select the default, connect to a host or domain. Host name is Train11 in my case. It's going to prompt
me for the user name and password, and off we go. So let's see. So now basically what this does is it pokes around the VEA, which
I'll trust that you can do on your own. I'm not going to spend too much time here on that. I'll just give you couple idea of the screen
shots here. Okay here we go, here's Train11. Let's open up the -- we're not going to have any disk groups yet. See what the story
with the disks is. So I'm going to do a devfsadm and a vxdctl enable. Those are the commands that scan the device tree, and also
the command that scans the Volume Manager objects. So these two commands typically go hand in hand to find the disks on the

http://symantecpartners.vportal.net/media/symantecpartners/media/_generated/transcripts/t... 8/23/2011

Lesson 2: Install and Configure - Installing Storage Foundation and Accessing SF Interfac... Page 2 of 2

system. When I find the disks I should be able to do that, and there we go. And look how we have enclosure-based naming set up as
the default. So we happen to be attached to a Hitachi Data Services 9500 array with a alua support. And just to show you that I can
switch easily over to enclosure-based naming, I'm going to do vxdiskadm option 20. Yes I want to change the naming scheme, and
just like that the naming format's been changed. And now vxdisk list shows the real long, boring paths to the disk, or the actual
device name I guess that is with an S2 at the end. And that's fine, I have copy and paste to use so I'm not worried. So it's funny
though, the VEA's not picking this up quite yet, and that's expected, so we do a re-scan on the VEA. We go to our tasks list at the
bottom and we see it's re-scanning. And there you go, VEA picks it up. Now I have some disks to play with. Okay so we just did this
disk scan command, taking a look at the interface, and now we can basically just exit the VEA. Okay and that concludes Lab 2.

http://symantecpartners.vportal.net/media/symantecpartners/media/_generated/transcripts/t... 8/23/2011