The local remote office and branch office functionality is contained in a single consolidated pod designed for use with ROBO.

Figure 1. Pod Architecture for Remote Office and Branch Office


Pod Architecture for ROBO

Table 1. Required Number of Racks

Pod (Function)

Required Number of Racks (for full scale deployment)

Minimum Number of Racks

Comment

Consolidated Pod

1

1

One rack is sufficient for a consolidated pod.

With 1 rack, the consolidated pod requires a minimum of 4 ESXi hosts in order to contain the management components and a minimum set of user workloads. Additional hosts can be added to scale to achieve the supported maximum number of virtual machines in a ROBO configuration.

The quantity and performance varies based on the workloads running within the consolidated pod and the actual hardware configuration of the pod hosts.

Storage pods

1

0

Storage that is not vSAN storage is hosted on isolated storage pods.

Total

2 (if secondary storage is not located in the same rack)

1

Table 2. POD and Racks Design Decisions

Decision ID

Design Decision

Design Justification

Design Implication

ROBO-PHY-002

The consolidated pod is bound to a physical rack.

The Top of Rack switches are the layer 2 boundary. Any virtual machines on a VLAN backed network, such as vCenter Server and NSX controllers, will lose network access if migrated to a host in a different rack.

The design must include sufficient power and cooling to operate the server equipment. This depends on the selected vendor and products.

ROBO-PHY-003

Each rack has two separate power feeds.

Redundant power feeds increase availability by ensuring that failure of a power feed does not bring down all equipment in a rack.

Combined with redundant network connections into a rack and within a rack, redundant power feeds prevent failure of equipment in an entire rack.

All equipment used must support two separate power feeds. The equipment must keep running if one power feed fails.