2 hours 58 minutes
Hi, you're watching model to US X. I envy Center server
Lesson five v Center Server Appliance Deployment types.
By the end of this video, you'll understand the different options you have for deploying be center server appliance.
So, as we said earlier, the V Center server appliance is the way to go. If you want to deploy recent,
let me remind you again that the appliance is a virtual machine that will run on Annie's Ex I host.
And there are two options to deploying this appliance.
The first option is having the PSC entry Center deployed as a single virtual machine,
with all the service's from both running together. This is the most popular option. If your company has a single site,
the second option is having the PSC Alfie Center deployed as two separate PM's
with the PSC in its on VM, you can share the service is within the PSC Among multiple V Center instances. This is very useful if your company has multiple sites,
so with this type of deployment, all recent instances will be linked to the same PSC for authentication,
so a user will be able to log into any off the V center instances and to manage all the other sites from a single interface.
We call this architecture in hast linked mode or E l m
enhanced link mode lets you link up to 15 V center instances and you can log tow any off them and have control over all of them.
But in house link mode has a weakness.
Do you see what it is?
Well, what if the PSC fails,
you're doomed. You cannot look into any off the V's under instances, because authentication, remember, is handled by the SS Oh, service, which runs on the PSC.
So what do you do then?
Well, to provide redundancy, you deployed two or more peces instead of one.
Then you length, um, in the network, and they will constantly synchronize so that both hold exactly the same data at all times. Then you hide them behind the load, balancer.
Why is that?
Well, because of these, enter instance can only be linked toe only one PSC at a time.
On the roll off the load balancer here is to represent both PS ease with a single public I P address.
Then you point your re center instances to the address off the load balancer and wallah.
Now, if one of the PSC is fails, the other one will support all the authentication requests.
Now. One more thing was pointing out,
starting with the Sphere 6.5 updates to It's now possible to have several embedded PSC deployments in an enhanced link mode. It's called embedded enhanced Link mode. This is an interesting one because it doesn't require a load balancer, and it's easier to set up.
It supports a maximum of 10 V center instances
I know come flooding you with information, and you might be wondering, how in the world am I supposed to remember all of this?
Watch this video over and over, and eventually it will stick.
Now let's recap.
The central Server appliance is the recommended installation type by Veum, where
it has two components. The V Center or V P X D, which is the management role,
and the platform service's controller, which is the authentication role.
The appliance is deployed as a virtual machine on in the SX I host.
There are two deployment options the embedded PSC option for a single site
and the external PSC option for a multi side.
Now, multiple re centers are instances can be linked to a single PSC. And we call this the enhanced link mode.
Thanks for watching.