Administrator Guide
Table Of Contents
- Dell Hybrid Cloud System for Microsoft Cloud Platform System Standard Version 1.5 Administrators Guide based on release 1803
- Overview
- Administration
- What to do first
- Next steps
- Managing Dell Hybrid Cloud System for Microsoft
- Creating tenant VM networks
- Adding tenant VM networks to the cloud
- Flagging the operating system VHD in the VM templates
- Enabling guest-specified IP addresses in VMM
- Creating additional tenant storage shares
- Using Windows Azure Pack
- Default Windows Azure Pack configuration
- Before you go into production
- Setting up tenant portal access on an isolated network
- Replacing self-signed certificates
- Disabling the tenant AuthSite and the admin Windows AuthSite websites
- Updating to a Security Token Service and re-establishing trust
- How to open the management portal for administrators
- How to open the management portal for tenants
- Offering services to tenants
- Optional configuration
- Automating tasks for efficiency
- Windows Azure Pack API reference content for developers
- Configuring disaster recovery protection
- Operations
- Monitoring
- Backup and recovery
- Onboard to Azure Backup
- Default backup schedule and retention policy
- DPM protection groups
- Disable machine account password rotation on management VMs
- Protecting tenant VMs
- Recovering VMs and databases—high level
- Recovering from management component failures
- Recovering a tenant VM
- Recovering DPM from DPM failures
- Adding extra disks to DPM
- Monitoring DPM
- Using the Dell Hybrid Cloud System for Microsoft data consistency runbooks
- Updating the Dell Hybrid Cloud System for Microsoft
- Shutting down and starting up the stamp
- Security
- Appendix A Expanding the stamp
- Appendix B Performing a factory reset
- Appendix C Retrieving cluster names, host names, and IP addresses
- Appendix D Ports and protocols
3 Install Java version 7 on this laptop so that you can start the virtual console through the iDRAC interface.
Ensure that AD DS services are available
Ensure that your Active Directory Domain Services (AD DS) infrastructure is available, and functional.
Step 1 Power on the hardware devices
1 Power on the PDUs.
2 Ensure the on/
o switch is on for the JBODs.
Step 2 Power on the le serv
er cluster hosts
1 Power on the le serv
er cluster hosts by using either of the following methods:
• Use the on/
o switch on the front of the server, or
• If the iDRACs are connected, connect to the IPv4 iDRAC address of the host from the laptop that is connected to port 39 or 40 of
the s
witch by using a browser, for example, open https://192.168.164.131.
2 Expand
Overview-Server-Power/Thermal. Click the Power Control tab. Click Power on System, and then click Apply.
3 Ping the le serv
er cluster hosts until they respond. It might take 10-20 minutes for them to be reachable.
4 When the le serv
er cluster hosts start responding, use the iDRAC to connect to one of the hosts and start a virtual console. Log on
with an account that is a member of the <
Prex
>-Ops-Admins group, open Windows PowerShell, and then run the following
commands:
a Get-StorageEnclosure to verify that all enclosures are online.
b $p = Get-PhysicalDisk followed by $p.count.
c Get-StoragePool to verify that the pool has been discovered and to view its health state.
d Get-VirtualDisk to verify whether all the storage spaces are online.
After you verify that the storage is running and healthy, continue to the next step.
Step 3 Power on the compute cluster hosts
1 Power on the compute cluster hosts by using either of the following methods:
• The on/
o switch on the front of the server, or
• If the iDRACs are connected, connect to the IPv4 iDRAC address of the hosts by using a browser, for example, https://
19
2.168.164.133, on the laptop that is connected to port 39 or 40 of the switch.
2 Ping the compute cluster hosts until they respond. It may take 10-20 minutes for them to be reachable.
Step 4 Power on the infrastructure VMs and tenant VMs
Use Remote Desktop Connection to connect to the Console VM with an account that is a member of the <
Prex
>-Setup-Admins group.
NOTE: You might have to wait an hour or longer from the time you turned on the compute cluster hosts to perform this step.
1 Open Failover Cluster Manager.
2 Connect to the compute cluster.
3 Click
Roles. Check the state of the VMs. The <
Prex
>CON01 VM should be running.
4 From Failover Cluster Manager, start the following infrastructure VMs:
a <
Prex>SQL01
b <
Prex>SQL02
5 Wait until the VMs in the SQL Server guest cluster are in a
Running state.
6 From Failover Cluster Manager, connect to the SQL Server guest cluster (<
Prex
>SQLCL.) Click Roles, and verify that both
instances (SQLIN01 and SQLIN02) are online. If not, right-click the role, and then click Start Role.
106 Operations