Well, it's time we've arrived at that point finally where we are going to install the FMC Vea in IWC.
As you saw, the prep work of IWC is really the bulk of our work, the deployment of the FMC.
Once you've done all that great work, it is very simple.
As you're about to see.
We're going to start things out at the IWC marketplace.
No surprise where the FMC V is ready and waiting for us to deploy it.
So here we are in the IWC management console and I am going to actually do a search on a US marketplace.
Now actually this is funny.
I don't want the marketplace of subscriptions, which is going to be specifics about subscriptions that
I've already made.
So I'm actually going to launch a new tab here and let's go to the IWC marketplace.
Outside of the console there, we go to the Marketplace homepage.
All right.
Now notice it has us as logged in.
There's our my account admin account.
So that's perfect.
And I'm going to search for fire power.
And there is the FMC virtual bring your own license.
That is the one we want, by the way, the step by step instructions for all that IWC prep that we did.
If you want those, it's down here under the support information.
So there's the Cisco link which will bring you to all the documentation, including a step by step guide
on how to prep your IWC environment.
All right, so here we go.
I'm going to continue to subscribe.
It's going to cost us about $0.68 an hour to run the FMC.
And that cost, by the way, is going to be a direct result of the instance, a big, large instance
that we have to spin it up with.
So that's the charges.
Sysco notice is not charging for the software.
We're bringing our own license.
In our case, that will be an EVO license.
But, you know, so because you're going to be bringing your own license, there's no software charges.
We're just going to be spinning up a CE three for X large, and that's where the cost comes in, that
hourly cost of the hardware.
All right, so we are going to, uh, I believe we're all set.
You have subscribed to the software.
Okay, there's the terms.
I want to continue to the configuration.
Forgive my pausing here, but, you know, this interface changes.
All these interfaces change so frequently.
All right, so this looks good.
And the monthly estimate, if we left the thing running would be 490 a month.
We're not going to leave the thing running, though.
So this should cost you like 5 to $6 a month if you're just spinning it up for, you know, 2 hours
worth of lab practice and then shutting it down.
All right.
So here we go.
We want the 64 bit RMI.
We want the very latest, greatest version and we want the U.S. East region.
And that all looks good.
So I am going to say continue to launch.
And what we're going to be doing, of course, is launching this inside of the DC two console.
So I'm actually going to launch through Easy EC2 and that's going to give me the full flexibility of
features as I'm configuring our FMC virtualized instance.
All right.
Now, we can't deploy this on any of that, you know, small, inexpensive stuff.
Let's do a let's see, I'll just do the C five for x large with its 16 virtual CPU's 32 gig.
I'm not worried about costs here because again, I'm going to be very conscientious to shut this thing
down when it's not in use and it's not going to be in use most of the time.
All right.
What are VPC is this going to live in?
In of course, that is the VPC that we created in an earlier video.
That's my FMC VPC.
And notice, the management subnet is the first subnet.
And it is selected.
That's perfect.
That's exactly where we want that to go.
And we do.
What do we want as far as the auto assignment of a public IP?
Well, yeah, it's fine to automatically assign it, but we actually have the elastic IP address that
is going to be in use.
So that's wonderful.
That's what we'll be using to connect to this FMC virtualized instance.
All right.
So nothing on any of this.
What we now need is let's see.
Yeah, we are all good on all that stuff.
Here is our network interface choice.
So this is important.
I want to choose that network interface that we had set up that has the elastic IP address assigned
to it.
And notice we can say manually assign.
No, no, no, we're going to say automatically assign.
And again, the elastic IP is going to swoop in and help us out.
All right.
So everything looks good up here.
And now what we want to do is I want to go ahead and feed this image some data as it spins up.
So Cisco gives us these instructions.
We're going to type hashtag FMC and then we are going to type in some JSON, it looks like to me.
So we do a quote and we say admin password and end quote.
We do a colon and then we are going to provide the admin password that we want.
I'll do Cisco, one, two, three and we then do a comma.
I just want to make sure I get this right, that's for sure.
And I could have copy pasted in here, but we all know that many times a copy and paste from a document
like a PDF can make things go haywire.
We'll call this FMC v-1 for a hostname and we are good to go.
Let's close off that JSON stanza and let me just check this admin password that looks perfect.
Hostname that looks perfect.
Close the brackets there.
Yeah, that's great.
Next up, we are heading to storage and it is pre-selected a 250 gig route volume.
We'll put that on the general purpose SSD.
And when we destroy this virtualized instance, this route volume will also get destroyed.
Next, we're going to add some tags.
We give this a name tag of SC to underscore FMC V and we're going to give the use tag and that's going
to be FMC in a WAC.
There we go.
Next up is the security group, and we created a security group for this purpose.
So all we need to do is select it and then review our options and launch this.
Now, what it's warning me about here is that we've gone outside of the free tier, so we're going to
get a monthly bill to our credit card.
And it's also telling me that my security group is lame, but we know it's lame.
And that's because we are not really worried about security for this demonstration.
It's lame, you recall, because it is not locking down management access to select IP addresses.
It's open to every IP address.
All right.
Let's see.
So this is just information about the am I and this all looks great.
And so I am going to say launch.
And of course, we need a key pair.
So I'm going to go ahead and create a new key pair of type RSA.
This is how we're going to make our secure access to this image.
And I'll give a name of FMC underscore in underscore IWC, and you're not surprised about that.
And then we download this key pair and when we make sure that download was successful, we then say
launch instance and we are now going to sit and patiently wait.
And that's because.
The FMC v when it is first initially spun up, it is going to take quite a bit of time to initialize.
All right.
Now, what happened here?
You cannot specify tags for network interfaces.
If there are no network interfaces being created by the request.
I'm going to get rid of these tags right here on the network interfaces because that's the silly little
thing that's causing the problem.
Look at that.
All right.
So I'm going to say review and launch.
And launch.
And one of the things that this troubleshooting did have me remember is that I have a setting under
the network interface card that I do want to manipulate.
So I'm glad we had some trouble.
And it got me thinking about the network interface card because I want to show you a setting we forgot
to make when we set up the network interface card.
And I think I can show you that right now as our instance is launching and like I said, we have quite
a bit of time to kill because this fancy V will take about 20 minutes typically before you can access
the command line and then get to the graphical user interface and we'll be doing that together.
So anyways, let me go to easy to here because there's a setting on our NIC we need to make and.
All right, there it is.
There is our NIC and let's see if it will let me manipulate it, especially now that it's in use.
We are going to change the source destination check and you want to go ahead and disable that.
So you want to make sure that your NIC for the FMS c v is not doing that source destination checking.
All right.
Excellent.
That's per Cisco to get it to work.
Right.
All right.
So now what we can do is we can go up to our easy to dashboard and we can just sit here and take a look
at our FMC v in the easy to dashboard, we notice it's in the running state.
And what we're going to be doing shortly is we're going to be selecting it and then going up here to
the Kinect and we will get our sage client instructions in how we are going to access the system.
Except we won't be going in as route, right will be going in probably as admin or whatever it is that
Cisco tells us to go in as.
So the key here is, though, I can't do any of this yet.
No.
I need to go ahead and just be patient.
I'm going to pause this video, the first boot of the FMC v inside of AWB.
I have experience with this.
It's going to be like really wait 20 or 30 minutes, you know, just set a timer and that's what I'm
going to do right now.
And then after 30 minutes, I'm going to come in and obviously unpause the video and record live as
we go in and access the command line of the FMC v and then of course hit the graphical user interface
over the Internet for this image.
So we'll complete this deployment by testing it once we give 30 minutes for this initial boot of this
massive Cisco software image.
All right.
Well, I do believe I have waited long enough.
Good 30 minutes.
So let's see what we can see when it comes to this virtual appliance.
So we're going to do is copy.
Let me show you how to get here.
Again, we have our instances and you can just select your EC2 instance and go to the connect button
and then you can get the same syntax you need.
Now what I've done on this Windows Box is I've gone and changed into the directory where that PEM file
is.
We downloaded for the authentication, the key pair.
And so I'm in the directory of downloads where I downloaded that too and I'm going to paste in that
syntax.
But we are going to make one change.
We're not logging in as root, we're logging in as admin on the FMC.
V All right.
So I hit Enter and oh, look at this.
So we are seeing that the fire power extensible OS is initializing.
And so yeah, the system is booting and clearly this is a great sign.
So I'll pause here and I'll keep an eye on this.
And the minute anything interesting happens, I'll unpause so you can see it as well.
All right, well, I'll say something's happened.
We just got yelled at.
And that's because and you know, I really did think of this when I was doing it earlier in the video
when I was putting in that stupid, silly default, you know, Cisco, one, two, three, lab password.
I really was worried that it would not be accepted.
And sure enough, it wasn't.
Okay, so no problem.
I will put in a serious, you know, strong password here and that will.
Make the FMC v very happy.
And look at this.
I think we are at the c ally here.
Yep.
Of the FMC v.
So this is certainly a great sign.
And I'm not going to do anything here, actually, because now I'm going to head to the gooey, right?
So of course, as Todd will teach you, key validations and things that you can do at the CLIA of the
FMC.
V This is proof enough for me and we've got a nice strong password set.
So now I'm going to head over and we are going to access this device of course in the graphical user
interface.
I was playing some online poker earlier there, so it's pretty funny.
We had a a poker URL.
All right, so what am I looking for?
I am looking for the public IP address.
Yes, indeed.
That is on the clipboard now.
And we are going to paste that in and look at this.
This is looking good.
It's going to bark about the certificate, of course, but we're going to say no problem, we know who
it is.
And there's the fancy we're going to be logging in with admin and that new super strong password that
I put in.
And there we go, folks.
We are at the FMC and it says, okay, you can configure licensing now or later to configure licensing.
Now register your device.
Or what we can do is right here, we are going to start the 90 day evaluation period without registration.
Thank you very much.
So I will save that.
And look at this.
We are in and there is that beautiful console of the FMC.
And of course we could go up and oh boy, it's been a while since I've messed with this under the deployment
area.
Sure, we would go in and start now.
It wouldn't be deploy, would it?
It would be probably under management where we start adding devices in.
Right?
I don't know.
All right.
I'll stop making a fool of myself.
Probably.
Devices.
Yeah.
Device management.
There we go.
And, you know, we.
Oh, that's where it started me out.
It had dropped me off where I needed to be, so we'd go in and start adding our devices here.
All right, I'll stop really embarrassing myself at this point.
And there it is.
The glorious FMC inside of AWB is running brilliantly.
Now I'm going to go ahead and gracefully shut it down.
So I'm going to go ahead and log out because remember, it's costing me pennies right now.
So there I am, I'm out.
I'm actually going to go over to the command prompt and log out.
There we go.
And I am now that I'm out of my beautiful FMC, I'm going to go up to the EC2 dashboard.
I'm going to go to my running instance and I am going to say, Ah, you know what I think I want to
do here?
You know, the graceful way to shut this down is actually going to be the FMC v c ally, isn't it?
Yeah.
So really I would want to shut it down that way.
So let me demonstrate that best practice.
Right?
So what I want to do, I want to go back to connect.
I want to copy that.
I want to go back to a command prompt.
Where are you?
All righty.
We're going to change to my downloads directory.
We're going to paste in this S-H syntax once again, going to admin there and.
All right, so what commands are available to me here are I think I need to change to system mode.
Right.
And then I need to shut down.
Beautiful boy.
There's been a while.
This command will shut down the system.
Yes.
All right, beauteous.
So that's how we are going to gracefully shut down the FM.
See, V.
Now, what you can do is you can come over to the EC2 instance area.
It's going to show it as running, but wait a few minutes and then come on, come in here and refresh.
And we should see that the console has picked up on the fact that that instance has shut down.
So I'll pause the video here and I'll wait a few minutes and then unpause the video so you can see the
confirmation.
All righty.
Yeah, I just hit refresh, and the EC2 instance disappeared, and that's because there was this running
filter.
So if I get rid of the running filter, there it is in the process of stopping.
And so we have no charges right now that are incurring against us except for there would be one little
charge and that's the elastic IP address.
So there would be a slight charge incurred with the elastic IP.
Now, couple of pennies, no big deal.
But they're upset with us now because we're consuming an IPv4 address that is not doing anything.
By the way, you know, if you did want to just it would be inconvenient, but you could run this without
the elastic IP and just get a different public IP address every time and be tracking that.
But yeah, I am incurring a few pennies now.
Like I said, the elastic IP address, no charge when it's in use.
So that's just a really interesting one.
But the bulk of the charges we don't have to worry about now, and that's because our FMC V is now stopped
in the console.
Now, just a few last words here.
If you wanted to clean all of this up, well, you would begin with terminating the instance.
And then once the instance is gone, you could start cleaning up all of those VPC components that you
created, the, you know, security group, the subnets.
I mean, you can just peel back all of these layers once your instance is gone.
So very simple to clean up.
And you could even use those tags as an easy way to find all of this lab stuff that we built.
Well, thank you so much for watching this mini course on the deployment of the FMC inside of IWC.