Creating groups, Figure 23, Allocation strategies – ClearCube Grid Center Admin Guide 4.11 User Manual

Page 48

Advertising
background image

Figure 23 Allocation Strategies

Mapping

Not Allowed

Valid

Mapping

I/Port Group

I/Port Group

I/Port Group

I/Port Group

I/Port Group

I/Port Group

Spare

Blade Group

Shared

Blade Group

I/Port

I/Port

I/Port

Dedicated

Blade Group

42 • Allocation

Grid Center 4.11 Administrator’s Guide

When a Blade group is designated as a Spare group, I/Ports can be re-mapped, or

spared, to any available Blade in that group, regardless of their allocation to a

Dedicated or Shared Blade group.

For example, the I/Ports in an I/Port group named “Sales I/Ports” could be configured

to connect only to the Blades in a Blade group named “Sales Blades.” When an end

user logs in, the Grid Center Console directs that user to a specific Blade, or to any

Blade in a particular group, as allocated.

Figure 23 shows the possible ways in which I/Ports, I/Port groups, Blades, and Blade

groups can be allocated, or mapped.

Any number of I/Port groups can be mapped to a Spare Blade group by using the

I/Port group configuration tools. Spare Blade groups are not displayed as selectable

groups in the Allocation View. Only one I/Port group can be mapped to a Shared

Blade group. I/Port groups cannot be mapped to Dedicated Blade groups. However,

individual I/Ports can be mapped to a Dedicated Blade in any quantity and from any

I/Port group.

Note: The Microsoft license restricts RDP connections between Blades and I/Ports

to no more than four simultaneous RDP connections per Blade. If more than

four I/Ports are mapped to a Blade, only the first four RDP connections

initiated will connect successfully.

Creating Groups

Before allocating I/Ports and Blades, you must first create I/Port groups and Blade

groups.

Advertising
This manual is related to the following products: