24PinTech Wiki - User contributions [en]

VSphere

2023-05-09T16:20:57Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password or using your personal account with @mhs.24pin.tech. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Download the latest version of VMware vCenter Server Appliance 7 for Essentials Plus from VMWare's [https://customerconnect.vmware.com/downloads/ customer connect site] using chamberlain's account.
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, choose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the [https://docs.google.com/document/d/1Gf5gtAfNwkZgOogfzz0wzIFiiWA5Bs1wjLkq4wUFGkg/edit?usp=sharing configuration] for the machine and then deploy the OVF.
*Once the machine boots up and says you can [https://docs.google.com/document/d/1Gf5gtAfNwkZgOogfzz0wzIFiiWA5Bs1wjLkq4wUFGkg/edit?usp=sharing configure] it from the web interface go ahead and do so (login should be root and the password you set)
*When finished, go to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplication
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2023-04-24T15:32:39Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password or using your personal account with @mhs.24pin.tech. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Download the latest version of VMware vCenter Server Appliance 7 for Essentials Plus from VMWare's [https://customerconnect.vmware.com/downloads/ customer connect site] using chamberlain's account.
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, choose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configuration] for the machine and then deploy the OVF.
*Once the machine boots up and says you can [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configure] it from the web interface go ahead and do so (login should be root and the password you set)
*When finished, go to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplication
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

DHCP

2023-04-06T22:09:06Z

Kwalters:

[[Category:Windows]]
=Our DHCP Setup=

Our DHCP is run on [[Odin]] and [[Friia]]. DHCP is what gives out the IP addresses to the devices on our network. Without it, we would have to use static IP addresses, or we would not be able to communicate properly. Both of the servers keep each other synced on what IP addresses have been given out to ensure there are no conflicts.

==Address Pool==

Our scope is 10.21.25.0, as that is our network. The DHCP server only distributes addresses in from 10.21.25.30 to 10.21.25.247. The rest in the network are reserved for servers and printers, or anything else that needs a static IP. The following chart represents our current setup...
{| class="wikitable"
|+Reservations
!Hostname
!IP Address
|-
|Gateway
|10.21.25.1
|-
|Valhalla
|10.21.25.2
|-
|Fenrir
|10.21.25.3
|-
|Friia
|10.21.25.4
|-
|Yggdrasil
|10.21.25.5
|-
|
|10.21.25.6
|-
|Asgard
|10.21.25.7
|-
|Heimdall
|10.21.25.8
|-
|
|10.21.25.9
|-
|Midgard/TrueNAS
|10.21.25.10
|-
|Logan
|10.21.25.11
|-
|Sleipnir
|10.21.25.12
|-
|
|10.21.25.13
|-
|Blackadam
|10.21.25.14
|-
|
|10.21.25.15
|-
|
|10.21.25.16
|-
|IOlan
|10.21.25.17
|-
|OpenGear
|10.21.25.18
|-
|
|10.21.25.19
|-
|
|10.21.25.20
|-
|vMotion (Val)
|10.21.25.21
|-
|
|10.21.25.22
|-
|vMotion (Asg)
|10.21.25.23
|-
|
|10.21.25.24
|-
|
|10.21.25.25
|-
|vSphere Rep
|10.21.25.26
|-
|
|10.21.25.27
|-
|Datacenter Switch
|10.21.25.28
|-
|FOG
|10.21.25.29
|-
|3D Print
|10.21.25.129
|-
|LaserPrint
|10.21.25.241
|-
|LaserColorPrint
|10.21.25.243
|}

==Address Leases==

These are all of the current DHCP releases that the DHCP servers have put out that are active.

==Reservations==

This is where all of our static DHCP-side reservations for our servers, printers, NAS, etc., are located. You can double click any of them to edit their specific settings.

==='''Hostname IP address'''===
LoganWeb (VM on Valhalla) 10.21.25.11

NAS 24PinTech 10.21.25.16

SC-P8000Series-2D6580 10.21.25.90

NPI7C274C (HP LaserJet P4014) 10.21.25.241

NPI82FF0E (HP Color LaserJet M553) 10.21.25.243

==Scope Options==

This is where we configure our DHCP options. To configure options that we don't already have set, right click "Scope Options" and click on "Configure Options" and configure what you need. Below are the options we already have set:

[[File:DHCP_Options.PNG]]

These options set where the computers will look for DNS, what our domain name is ([[CISCOACA.local]]) and the other options tell computers to PXE boot from [[FOG]] and configures the settings they need to boot from [[FOG]].

==Policies==

These are settings that are applied to certain devices based off of rules defined by the policy, like IP address range, vendor, etc.

The only policy we have currently configured is called UEFI, which applies to network booting via UEFI. It sets options 66 and 67 to make sure devices will boot properly off of [[FOG]]. 67 is set to ipxe.efi, and 66 is set to 10.21.25.4.

==Server Options==

This is where settings can be configured globally across the whole DHCP server. We have none of these currently configured.

==Policies (Not within scope)==

Same as above policies but global, we do not have this configured.

==Filters==

This allows you to block or allow certain MAC addresses from receiving DHCP addresses.

ESXi

2023-03-28T20:22:14Z

Kwalters:

[[Category:VMware]]
==What is it==
[[File:VMwareESXiHostClientSummary.png|thumb|640x640px|General image of ESXi web interface|link=https://10.21.25.11//wiki.24pin.tech/File:VMwareESXiHostClientSummary.png]]ESXi is an OS designed to hold many virtual machines on one physical machine. It is identified as a type-1 hypervisor developed by VMware. We are using it currently for at least 4 of our machines in the classroom. Those machines are Heimdall, Thor, Asgard, and Valhalla. Heimdall and Thor are using the 6.7 license as explained in the Installation of ESXi heading. Asgard and Valhalla are using version 7.0+ which we paid for the licenses.
==Installation of ESXi==
The installation method of ESXi is pretty simple. All you will need is a computer/server and a flash drive. To be able to actually access the server you'll end up needing the machine to be connected to the internet. The procedure is as follows:

*Grab a image of ESXi from VMware's page. Depending on the importance or role of the server, you should use vSphere 6.7 for testing and small project purposes. Use 7.0+ as a limited resource since we only have so many activations available. You can grab all of our ISOs from the following directory on our domain, [https://10.21.25.11//wiki.24pin.tech/Mhs.24pin.tech mhs.24pin.tech], \\10.21.25.13/Cisco Curriculum/vSphere Downloads/ESXi ISOs/
*The rest of the installation process is pretty simple and can be found here: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-6FFA928F-7F7D-4B1A-B05C-777279233A77.html
*Once installed go to manage>licensing and input your license key, or you can use evaluation mode for up to at least 30 days. Though if you are using version 6.7 you can use the following key: 144AH-AU10P-W8888-0A22K-85912 and if you are going to use 7.0+ you can grab the product key from our vSphere Downloads folder from above.

==Management of a ESXi Machine's Local Interface==
[[File:VCenter interface.png|thumb|310x310px|link=https://10.21.25.11//wiki.24pin.tech/File:VCenter_interface.png]]After you install ESXi you should be greeted with a screen like shown to the right. (The screenshot is one of the vCenter server but a ESXi local interface should look similar)Through this screen you will be able to change management settings such as hostname, basic management networking, etc. A specific list of what you can do from the machine locally can be found below, to access these options you need to press f2 and use the login you created for the machine.

*Configure local password
*Configure lockdown
*Configure/Restart/Test Management Network and restore default networking settings
*Configure keyboard
*Troubleshooting Options
*View systems logs, support information
*Reset System Configurations

==Accessing ESXi's web interface==
To actually be able to get into ESXi you'll need to be able to access the server using a web interface. To get into the server simply put the ip address of the server into your web browser like this, [http://10.21.25.2/ http://10.21.25.2]. Once prompted to login, use the default username root and the root password you set during installation. You will be able to add the device to the domain and be able to create other users once logged in with root.
==Creating a VM==
Creating a VM on ESXi is pretty simple. The big thing is that you have to make sure your server/ESXi host has enough resources to share with it's VMs. You can create as many VMs as you want as long as you have the resources to see fit. Its best practice to try to limit your resources you give to a single machine to a minimum. For example, you won't be giving a domain controller tasked with basic tasks such as DNS, Active Directory, and DHCP 1 TB of storage and 32 logical cores. To determine the correct resources for your machine you'll want to research the best practices for that type of machine. The following is the steps of creating a virtual machine:[[File:Friia config.png|thumb|382x382px|Basic settings of Friia our secondary domain controller|link=https://10.21.25.11//wiki.24pin.tech/File:Friia_config.png]]

*Move into the Virtual Machines tab of ESXi as shown in the image at the top of the page.
*From there you will want to press create/register a VM
*You will be prompted with three options, to create a new VM, deploy a machine from OVF or OVA, or register a existing machine. For our purposes we will be creating a new VM.
*Next you will want to enter the name of the VM (this is only for the ESXi interface and has no effect on the VM itself) and choose what OS the VM will be. This is for management purposes.
*The next step asks you where you would like the machine to be actually located. This gets pretty in depth and lets you choose a storage point other than the local machine. Choosing a storage point other than the local machine is usually used when implanting redundancy. For our purposes we will be choosing the local storage.
*Now you actually get to assign the resources to your VM. You'll be able to set how many logical cores, ram, and storage the VM has. Once again do research on what the basic requirements of the VM you are creating. When choosing your networking settings use the machines default for now. This can get pretty in depth but once again we are staying basic here. Here you will also be able to choose the ISO file you are using to setup the machine. You simply want to choose it as a CD drive and upload the image either through the network or locally though a USB.
*That's it. Now you can go ahead and finalize the process of creating the VM.

==Adding ESXi to the domain==
Adding ESXi to the domain can easily be done by heading over to the manage tab on the left of the ESXi web interface. From there you will want to go into the Security & Users tab and down into Authentication. You should see something like this screenshot below. Here you will be able to press join domain. All you will have to do is enter the domain name, in our case mhs.24pin.tech and a admin login for that domain. Only users in the ESXi user group and Domain Admin group will be able to access ESXi.[[File:Asgard Domain.png|thumb|601x601px|link=https://10.21.25.11//wiki.24pin.tech/File:Asgard_Domain.png|none]]

=== User Permissions: ===
User and group permissions can be modified by going to permissions under actions.
[[File:Image2424.png|none|thumb]]
Customs roles can also be created to allow certain user groups to have specific permissions. Our environment has a user group for users that need basic access to ESXi
[[File:354253.png|none|thumb]]

==ESXi Networking==
===Brief Overview===
The ESXi machine basically has its own local environment built into it. Once you setup the machine and access the networking portion from the web interface you'll see that the machine has it's own vNICs, vSwitches, vVLANs, etc. If you want to get experienced with ESXi and know how to manage machines networking wise you'll need to know about these. A brief breakdown of this networking portion is that you'll have a VM Port group all assigned to a Virtual Switch which connects the VMs to the physical NICs. You can do many other things with this networking environment like making closed off test environments, separating VLANs, and configuring VMWare offered features like vMotion.
===Management===
When you initially setup the ESXi machine you create a management IP address. This is used to initially setup the machine and to access the web interface whenever you need it. You could also use the DNS name of the server once that is setup as well. If anything ever goes wrong on the networking side and you can't remotely access the server, you may need to go into the local server and reset the networking on the machine. This could be done easily with the following steps:

#Go into the local machine and press F2, it will ask for the root login that you created on initial setup.
#This interface is used to change anything management wise for the ESXi machine. (You can reset root password, reset networking, etc.)
#For our purpose we will go into the reset management network, what this will do is reset the NICs on the machine and VLANs that way it goes back to its original setup, this will usually fix networking issues.
#In this interface you can also edit the assigned VLAN, NIC teaming, etc. It is very helpful for troubleshooting.

===NIC Teaming===
Whenever you plug in a new cable to the physical machine it should automatically pick it up as a physical NIC and assign it a MAC address. To actually assign all the other cables other than the management cable to a interface on the machine you'll need to manually assign it to a Virtual Switch. After that you have to make and assign all the VMs to a port group and assign that port group to the switch that is connected to the NIC team. The process of creating a NIC team can be followed with this process:

#Open up the web interface for the ESXi machine. For my example I will be using Valhalla (10.21.25.2)
#Go to the networking portion of ESXi which can be found on the list of drop downs to the left.
#You'll see multiple tabs including Port Groups, Virtual Switches, Physical NICs, VMKernel NICs, TCP/IP Stacks, Firewall Rules. We can leave VMKernel, TCP/IP Stacks, and the Firewall alone for now.
#Go into the Physical NIC tab to verify that all of your NICs are activated and plugged in.
#Next you will want to create a new Virtual Switch (by switching to the Virtual Switch tab and pressing add new switch), name this something that you'll easily identify.
#Leave pretty much everything the same and click add.
#Once the virtual switch has been made you'll want to click create new uplink, these are the physical NICs and assigns them to the virtual switch.
#After assigning the uplinks go into the settings of the switch to verify that they are assigned. You can leave the rest of the settings the same, or change them depending on your purposes or knowledge.
#Now go into the Port Group tab. You can either use the default Port Group (recommended if you already have VMs running on the machine) or create a new one with your own name. If you do use the default Port Group you will have to go into the settings of it and assign it to the new vSwitch. These are what you will assign the VMs to so that they are connected.
#Once done you should verify all the connections of the VMs and make sure they are all connected to the correct Port Group. Ta-da you are done.

==Moving a pre existing machine to or from ESXi==
[[File:Word-image-51.png|thumb|442x442px|Starwind converter|link=https://10.21.25.11//wiki.24pin.tech/File:Word-image-51.png]]The process of moving pre existing machines onto ESXi and copying them off is pretty easy. You can do this by using [https://10.21.25.11//wiki.24pin.tech/Starwind Starwind]. [https://10.21.25.11//wiki.24pin.tech/Starwind Starwind] will allow you to choose a remote image, local file, or physical machine and put that image onto another machine locally or as a VM. It became pretty helpful in our process of virtualizing all of our physical servers onto one machine.

Another way of doing this could be through vMotion. This moves a VM from one vSphere machine to another while keeping the VM running and functional. Though to set this up you will need to assign a new vNIC to each machine the destination and source and that will require a IP address from our domain.
==Probable Issues==

*One day a cable came slightly unplugged and the domain controllers started acting up. The web server also had some issues. We don't know if this was the

==Helpful Links==
For those that would like more information than what I can provide:

*https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/virtual_networking_concepts.pdf #General piece on VMWare Virtual Networking, a bit dated
*https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-B57FBE96-21EA-401C-BAA6-BDE88108E4BB.html #Best practices, should probably follow
*https://www.youtube.com/watch?v=GkC6lLfVj50 Creating a mac VM

File:354253.png

2023-03-28T20:20:38Z

Kwalters:

32324234

File:Image2424.png

2023-03-28T20:19:10Z

Kwalters:

DHCP

2023-02-15T18:30:58Z

Kwalters:

[[Category:Windows]]
=Our DHCP Setup=

Our DHCP is run on [[Odin]] and [[Friia]]. DHCP is what gives out the IP addresses to the devices on our network. Without it, we would have to use static IP addresses, or we would not be able to communicate properly. Both of the servers keep each other synced on what IP addresses have been given out to ensure there are no conflicts.

==Address Pool==

Our scope is 10.21.25.0, as that is our network. The DHCP server only distributes addresses in from 10.21.25.30 to 10.21.25.247. The rest in the network are reserved for servers and printers, or anything else that needs a static IP. The following chart represents our current setup...
{| class="wikitable"
|+Reservations
!Hostname
!IP Address
|-
|Gateway
|10.21.25.1
|-
|Valhalla
|10.21.25.2
|-
|Fenrir
|10.21.25.3
|-
|Friia
|10.21.25.4
|-
|Yggdrasil
|10.21.25.5
|-
|Sakaar
|10.21.25.6
|-
|Asgard
|10.21.25.7
|-
|Heimdall
|10.21.25.8
|-
|Xandar
|10.21.25.9
|-
|Midgard/TrueNAS
|10.21.25.10
|-
|Logan
|10.21.25.11
|-
|Sleipnir
|10.21.25.12
|-
|
|10.21.25.13
|-
|Blackadam
|10.21.25.14
|-
|
|10.21.25.15
|-
|
|10.21.25.16
|-
|IOlan
|10.21.25.17
|-
|OpenGear
|10.21.25.18
|-
|
|10.21.25.19
|-
|vMotion (Val)
|10.21.25.20
|-
|
|10.21.25.21
|-
|vMotion (Asg)
|10.21.25.22
|-
|
|10.21.25.23
|-
|
|10.21.25.24
|-
|
|10.21.25.25
|-
|vSphere Rep
|10.21.25.26
|-
|
|10.21.25.27
|-
|Datacenter Switch
|10.21.25.28
|-
|FOG
|10.21.25.29
|-
|3D Print
|10.21.25.129
|-
|LaserPrint
|10.21.25.241
|-
|LaserColorPrint
|10.21.25.243
|}

==Address Leases==

These are all of the current DHCP releases that the DHCP servers have put out that are active.

==Reservations==

This is where all of our static DHCP-side reservations for our servers, printers, NAS, etc., are located. You can double click any of them to edit their specific settings.

==='''Hostname IP address'''===
LoganWeb (VM on Valhalla) 10.21.25.11

NAS 24PinTech 10.21.25.16

SC-P8000Series-2D6580 10.21.25.90

NPI7C274C (HP LaserJet P4014) 10.21.25.241

NPI82FF0E (HP Color LaserJet M553) 10.21.25.243

==Scope Options==

This is where we configure our DHCP options. To configure options that we don't already have set, right click "Scope Options" and click on "Configure Options" and configure what you need. Below are the options we already have set:

[[File:DHCP_Options.PNG]]

These options set where the computers will look for DNS, what our domain name is ([[CISCOACA.local]]) and the other options tell computers to PXE boot from [[FOG]] and configures the settings they need to boot from [[FOG]].

==Policies==

These are settings that are applied to certain devices based off of rules defined by the policy, like IP address range, vendor, etc.

The only policy we have currently configured is called UEFI, which applies to network booting via UEFI. It sets options 66 and 67 to make sure devices will boot properly off of [[FOG]]. 67 is set to ipxe.efi, and 66 is set to 10.21.25.4.

==Server Options==

This is where settings can be configured globally across the whole DHCP server. We have none of these currently configured.

==Policies (Not within scope)==

Same as above policies but global, we do not have this configured.

==Filters==

This allows you to block or allow certain MAC addresses from receiving DHCP addresses.

VSphere

2023-02-03T15:31:21Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Download the latest version of VMware vCenter Server Appliance 7 for Essentials Plus from VMWare's [https://customerconnect.vmware.com/downloads/ customer connect site] using chamberlain's account.
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, choose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configuration] for the machine and then deploy the OVF.
*Once the machine boots up and says you can [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configure] it from the web interface go ahead and do so (login should be root and the password you set)
*When finished, go to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplication
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2023-02-03T15:30:27Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Download the latest version of VMware vCenter Server Appliance 7 for Essentials Plus from VMWare's [https://customerconnect.vmware.com/downloads/ customer connect site] using chamberlain's account.
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configuration] for the machine and then deploy the OVF.
*Once the machine boots up and says you can [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configure] it from the web interface go ahead and do so (login should be root and the password you set)
*When finished, go to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplication
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2023-02-02T15:22:13Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Download the latest version of VMware vCenter Server Appliance 7 for Essentials Plus from VMWare's [https://customerconnect.vmware.com/downloads/ customer connect site] using chamberlain's account.
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplicationAsgard

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configuration] for the machine and then deploy the OVF.
*Once the machine boots up and says you can [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configure] it from the web interface go ahead and do so (login should be root and the password you set)
*When finished, go to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2023-02-01T18:21:59Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer or download the latest version of VMware vCenter Server Appliance for Essentials Plus from VMWare's [https://customerconnect.vmware.com/downloads/ customer connect site] using chamberlain's account.
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplicationAsgard

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configuration] for the machine and then deploy the OVF.
*Once the machine boots up and says you can [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configure] it from the web interface go ahead and do so (login should be root and the password you set)
*When finished, go to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2023-02-01T15:52:49Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer or download the VMware vCenter Server Appliance for Essentials Plus from VMWare's [https://customerconnect.vmware.com/downloads/ customer connect site] using chamberlain's account.
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplicationAsgard

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configuration] for the machine and then deploy the OVF.
*Once the machine boots up and says you can [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configure] it from the web interface go ahead and do so (login should be root and the password you set)
*When finished, go to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2023-02-01T15:49:00Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer or download the VMware vCenter Server Appliance Update Bundle from VMWare's [https://customerconnect.vmware.com/downloads/ customer connect site] using chamberlain's account.
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplicationAsgard

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configuration] for the machine and then deploy the OVF.
*Once the machine boots up and says you can [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configure] it from the web interface go ahead and do so (login should be root and the password you set)
*When finished, go to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2023-02-01T15:45:50Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer or download the VMware vCenter Server Appliance Update Bundle from VMWare's [https://customerconnect.vmware.com/downloads/details?downloadGroup=VC70U3J&productId=974&rPId=99916 customer connect site] using chamberlain's account.
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplicationAsgard

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configuration] for the machine and then deploy the OVF.
*Once the machine boots up and says you can [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configure] it from the web interface go ahead and do so (login should be root and the password you set)
*When finished, go to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

Proxmox

2023-01-31T20:04:26Z

Kwalters:

=== Installing Proxmox ===

# Creating A Bootable USB Drive:
## Download the ISO image of the version of proxmox that you want to install from <nowiki>https://www.proxmox.com/en/downloads/category/iso-images-pve</nowiki>. For our environment we will be using Proxmox VE 7.3.
## Once the ISO has finished downloading, use rufus to create a bootable USB drive for proxmox. The drive needs a minimum of 2 gb and will be completely wiped when turned into a bootable drive.
# Preparing To Install Proxmox:
## Put the bootable USB drive in the USB port in the front of the server and press the power button to turn it on.
## Press F2 to access the BIOS as it boots and then go to System Bios > Boot Settings. Go to the BIOS Boot Settings and then configure the Hard-Disk Drive Sequence to use the bootable usb drive first. Exit and save changes to go back to the main menu.
## Exit and save the changes again, this time fully exiting the bios. The server will automatically boot from the USB drive.
# Installing Proxmox:
## A screen for the Proxmox Installer should show up with 4 different options. Choose Install Proxmox VE and then accept the EULA.
## Pick the target hard disk to install Proxmox on.
## Select the Phoenix time zone.
## Enter the password and email ([[Mailto:24pintech@gmail.com|24pintech@gmail.com]] + password)
## Enter the same information that was used for the IDRAC settings in the network configuration.
## Confirm everything is correct and then press Install. Once the installation has finished, remove the USB drive and reboot.
## Proxmox can now be accessed on any web browser using the Static IP and port 8006. (<nowiki>https://10.21.25.6:8006</nowiki> or <nowiki>https://10.21.25.9:8006</nowiki>)

Xandar

2023-01-31T16:18:40Z

Kwalters:

Xandar is the secondary server that is used for Proxmox.

==== Specs: ====

* Model: PowerEdge R450
* Service Tag: D134WM3
* SSD: 480 GB
* HDD: 6 TB (6x 1TB)
* CPU: 48 x Intel Xeon Silver 4310 CPU @ 2.10GHz (2 Sockets)
* RAM: 64 GB @ 2666 MHz

Sakaar

2023-01-31T16:18:18Z

Kwalters:

Sakaar is the main server that is used for Proxmox.

==== Specs: ====

* Model: PowerEdge R450
* Service Tag: 2134WM3
* SSD: 480 GB
* HDD: 6 TB (6x 1TB)
* CPU: 48 x Intel Xeon Silver 4310 CPU @ 2.10GHz (2 Sockets)
* RAM: 192 GB @ 2666 MHz

Xandar

2023-01-31T16:09:42Z

Kwalters: Created page with "Model: PowerEdge R450 Service Tag: D134WM3 SSD: 480 GB HDD: 6 TB (6x 1TB) CPU: 48 x Intel Xeon Silver 4310 CPU @ 2.10GHz (2 Sockets) RAM: 64 GB @ 2666 MHz"

Model: PowerEdge R450

Service Tag: D134WM3

SSD: 480 GB

HDD: 6 TB (6x 1TB)

CPU: 48 x Intel Xeon Silver 4310 CPU @ 2.10GHz (2 Sockets)

RAM: 64 GB @ 2666 MHz

Sakaar

2023-01-31T16:09:21Z

Kwalters: Created page with "Model: PowerEdge R450 Service Tag: 2134WM3 SSD: 480 GB HDD: 6 TB (6x 1TB) CPU: 48 x Intel Xeon Silver 4310 CPU @ 2.10GHz (2 Sockets) RAM: 192 GB @ 2666 MHz"

Model: PowerEdge R450

Service Tag: 2134WM3

SSD: 480 GB

HDD: 6 TB (6x 1TB)

CPU: 48 x Intel Xeon Silver 4310 CPU @ 2.10GHz (2 Sockets)

RAM: 192 GB @ 2666 MHz

Proxmox

2023-01-04T15:49:10Z

Kwalters:

=== Installing Proxmox ===

# Creating A Bootable USB Drive:
## Download the ISO image of the version of proxmox that you want to install from <nowiki>https://www.proxmox.com/en/downloads/category/iso-images-pve</nowiki>. For our environment we will be using Proxmox VE 7.0 since the latest version does not currently work on the kvm switch.
## Once the ISO has finished downloading, use rufus to create a bootable USB drive for proxmox. The drive needs a minimum of 2 gb and will be completely wiped when turned into a bootable drive.
# Preparing To Install Proxmox:
## Put the bootable USB drive in the USB port in the front of the server and press the power button to turn it on.
## Press F2 to access the BIOS as it boots and then go to System Bios > Boot Settings. Go to the BIOS Boot Settings and then configure the Hard-Disk Drive Sequence to use the bootable usb drive first. Exit and save changes to go back to the main menu.
## Exit and save the changes again, this time fully exiting the bios. The server will automatically boot from the USB drive.
# Installing Proxmox:
## A screen for the Proxmox Installer should show up with 4 different options. Choose Install Proxmox VE and then accept the EULA.
## Pick the target hard disk to install Proxmox on.
## Select the Phoenix time zone.
## Enter the password and email ([[Mailto:24pintech@gmail.com|24pintech@gmail.com]] + password)
## Enter the same information that was used for the IDRAC settings in the network configuration.
## Confirm everything is correct and then press Install. Once the installation has finished, remove the USB drive and reboot.
## Proxmox can now be accessed on any web browser using the Static IP and port 8006. (<nowiki>https://10.21.25.6:8006</nowiki> or <nowiki>https://10.21.25.9:8006</nowiki>)

Wazuh

2022-11-18T14:54:23Z

Kwalters: /* Wazuh Manager */

Wazuh is the SIEM software that is used to make sure that all of our computers are up to standard in terms of system health and to monitor any security events. The Wazuh server lives on Valhalla in an Ubuntu virtual machine named Gustavo. There are also agents that are deployed onto each device which collect necessary information that will be needed to make a full report on any issues that may be occurring on said system. All of the data is then processed and sent to the manager which takes all of the data and organizes it into one source. It also utilizes Elasticstack which visualizes all of the data the manager has so that everything going on in 24Pintech's systems can be monitored without much hassle.

ㅤ

== Configuring Wazuh ==

=== Installation Process===
===='''Wazuh Manager''' ====
Install the manager using the process at https://documentation.wazuh.com/current/quickstart.html for APT. Once installed, the manager can be accessed through the web by typing in the IP address of system that the manager was installed on into the search bar '''(https://<manager ip>)'''. Once that is done, you will be taken to the manager page and type in the user name and password, then all of the information on the systems added can be viewed.

'''Wazuh Agent''' '''Windows Configuration'''

* Get Wazuh running on a computer that already has it installed
# Open command prompt ('''admin''')
# Run the command below
# <code>'''"C:\Program Files (x86)\ossec-agent\agent-auth.exe" -m 10.21.25.12 -P password'''</code>
# If this command worked you are done. If this command fails you need to remove the agent from the list.

* Get Wazuh running on a computer that does not have it installed

# In file explorer navigate to Cisco Curriculum in Midgard (Q:)
# Copy the Deployed Applications folder and paste it in C:
# Change the folder name to DeployedApplications
#Run Windows PowerShell as '''ADMIN'''
# Enter: <code>'''cd c:\DeployedApplications'''</code>
# Enter the command: <code>'''.\wazuh-agent-4.2.5-1.msi /q WAZUH_MANAGER="10.21.25.12" WAZUH_REGISTRATION_SERVER="10.21.25.12" WAZUH_REGISTRATION_PASSWORD="password"'''</code>
'''Wazuh Agent''' '''Mac Configuration'''

* Log in to the computer with the '''24pintech''' account. You may also open this wiki page on that computer to copy and paste commands.

* Open a terminal window and install Wazuh agent using this command: <code>'''curl -so wazuh-agent-4.3.9.pkg <nowiki>https://packages.wazuh.com/4.x/macos/wazuh-agent-4.3.9-1.pkg</nowiki> && sudo launchctl setenv WAZUH_MANAGER '10.21.25.12' && sudo installer -pkg ./wazuh-agent-4.3.9.pkg -target /'''</code> (If prompted, use the 24pintech account password to finish the installation)
* Run this command to start Wazuh: '''<code>sudo /Library/Ossec/bin/wazuh-control start</code>'''
* Verify that the agent has been added in wazuh after refreshing the page.

[[File:Image.png|thumb|This is the menu, also known as the agent manager that opens when you insert <code>'''/var/ossec/bin/manage_agents'''</code>]]
'''Wazuh Agent Manager'''

Running this command will open the menu to add, remove, and edit agents (see picture on the right)

<code>'''/var/ossec/bin/manage_agents'''</code>

* '''Add an agent (A)'''
By entering "A" you can add an agent to the list. All you need is to input the name of the computer you want to add and the computers IP address.
* '''Extract key for an agent (E)'''
By entering "E" you can get a new key for an agent. All you need is to input the ID number of the agent. This can be done to help get a new key however this is likely unnecessary as you just need to run one command from command prompt on the agent you are trying to give a key to. (See "'''Wazuh Agent Windows Configuration'''")
* '''List already added agents (L)'''
By entering "L" you can view a list of every agent and that agents ID number. This can also be viewed from the Wazuh manager page in more detail however this is often a very convenient command when you need to check the list for one agent.
* '''Remove an agent (R)'''
By entering "R" you can remove an agent from the manager by entering the agents ID number. This is useful to remove agents we do not need or to remove faulty agents to fix them and get them running properly.

* '''Quit (Q)'''

By entering "Q" you can close the menu and return to the normal terminal screen.

== Monitoring Wazuh ==

===How to Monitor===
There is a lot of information present on the manager page with details on everything connected. Mainly, all the information that will want to be looked at is present on the Security Events, Integrity Monitoring, Agents, and Manager tabs for the information that we will be troubleshooting and coming up with solutions for. The main thing that will need to be looked for are going to be any failures seen on one of the servers or workstations. You will also want to look at the agents connected to see if things are in order or not with connection to the manager. Another thing would be vulnerabilities detected by the manager within our systems and note what kind of vulnerability that it is. The processes being made will also be something that needs to be monitored for any issues on the systems.
===What to look for===
====='''Modules'''=====
*
'''Security information management'''
*Security Events
**Alerts - This will be the main place to look for all of the systems current events taking place as far back as you need to. This will go over any login failures, malware, or anything of that nature will be viewed here across all agents. The key to looking at this all is section through the level of alert going from 1 - 12 with each increase in level being a higher alert that needs to be looked at. Anything above 7 will typically be what is unwanted unless another technician is performing a task that is causing said alerts. Take the proper steps as listed within the policy when any alert is worth being taken to the higher ups for proper handling.
'''Auditing and Policy Monitoring'''
*Security Configuration Assessments
**Here will be the most important place to look as you will need to monitor for any faults detected in the system's security. One of each device (All servers need to be checked) and then you as a tech will need to research into the issue if it is important. If there is a major security issue then this can be dealt with either by informing a higher up and getting the all clear to fix it, or if you are already in charge of fixing the security of the systems.
====='''''Management'''''=====
'''Administration'''
*This will probably be the most unused section of the SIEM, but if multiple technicians ever take it on then here is where all accounts would be managed depending on the trust within that technician, so restrictions can be set to ensure that all users have the correct access on the server, ensuring that nothing will be used against policy. This is also where rules will be configured for the nodes and clusters mainly for what will be showed on the virtual machine
'''Status and Reports'''
*This is where you will be able to generate a status report of the SIEM as well as seeing the status of each manager/cluster. By generating a report you will be given a detailed pdf of everything that has been logged for when you set it and you will be able to go over it and see anything that sticks out instead of having to check each individual module on the SIEM. You will also view the cluster health by seeing if one of the nodes has gone down and needs to be repaired to get it in working order once more.
====='''Agent'''=====
*Any and all issues that are had within the agent monitoring page can be checked for in the troubleshooting section of the [[SIEM: Configuration|SIEM: Configuration wiki page]].
'''Active'''
*Here you will be looking for any and all agents connected to the SIEM. You will look here for any newly added agents that are supposed to be there as well as if they have properly connected.
'''Disconnected'''
*You will look here to see if any important agents such as the servers are disconnected due to it being turned off or if it has been inactive for quite a while as they may need to be reset which can be done in many ways.
'''Never connected'''
*This will be used to check for any agents that have been connected improperly due to human error or any oversight that had happened during the configuration. If this happens to occur then some of the issues with the setup of an agent should be able to be fixed by viewing previous troubleshooting, but if the issue is unknown, then consult either the Wazuh documentation or a manager.
===Reporting===
[[File:Email.png|thumb|Config for email|294x294px]][[File:Report.png|thumb|Config for reports|277x277px]]Reports from the manager can be set up to email the information directly to us. In order to do this the '''Ossec.conf file''' needs to be edited to set up automatic reports by using the command With this you can choose who will receive it, the frequency of emails, and the level of alert it will send an email for once your information is filled into the box. Once you have made it in there will be a section to input a sending email and the recipient email, whatever your purpose is for receiving the email will most likely be for the higher alerts that need fixing immediately.

This is the command needed to access the ossec.conf file on the virtual machine.

<code>sudo nano /var/ossec/etc/ossec.conf</code>

'''''Warning: Configuring the Ossec.Conf file on either of the nodes or the server web page can lead to the server malfunctioning. Make sure you know exactly what you are doing and/or you have a backup ready before changing anything.'''''

== Wazuh Commands: ==

====Agent Config (Agent Side)====

* <code>'''net stop wazuh'''</code>
** Stops Wazuh
* <code>'''net start wazuh'''</code>
** Starts Wazuh
* <code>'''Restart-Service -Name wazuh'''</code>
*<code>'''systemctl restart wazuh-manager'''</code>
** Restarts Wazuh manager
* <code>'''"C:\Program Files (x86)\ossec-agent\agent-auth.exe" -m 10.21.25.12 -P password'''</code>
** Obtains a new key and activates an agent
==== Agent Config (Server Side)====

* <code>'''/var/ossec/bin/manage_agents'''</code>
** Opens agent manager. More info on the manager under "'''Wazuh Agent Manager'''"

====Server Config - Nano====

* <code>'''systemctl start/status/stop/restart wazuh-manager'''</code>
* <code>'''/usr/share/kibana/data/wazuh/config/wazuh.yml'''</code>
* <code>'''/var/ossec/etc/shared/dbms/agent.conf'''</code>
* <code>'''/var/ossec/etc/ossec.conf'''</code>
* <code>'''/etc/filebeat/filebeat.yml'''</code>
* <code>'''/etc/kibana/kibana.yml'''</code>
* <code>'''/var/ossec/bin/wazuh-control -j info'''</code>
* <code>'''/var/ossec/logs/active-responses.log'''</code>

Wazuh

2022-11-18T14:49:39Z

Kwalters: /* Wazuh Manager */

Wazuh is the SIEM software that is used to make sure that all of our computers are up to standard in terms of system health and to monitor any security events. The Wazuh server lives on Valhalla in an Ubuntu virtual machine named Gustavo. There are also agents that are deployed onto each device which collect necessary information that will be needed to make a full report on any issues that may be occurring on said system. All of the data is then processed and sent to the manager which takes all of the data and organizes it into one source. It also utilizes Elasticstack which visualizes all of the data the manager has so that everything going on in 24Pintech's systems can be monitored without much hassle.

ㅤ

== Configuring Wazuh ==

=== Installation Process===
===='''Wazuh Manager''' ====
Install the manager using the process at https://documentation.wazuh.com/4.2/installation-guide/open-distro/all-in-one-deployment/all-in-one.html for APT. Once installed, the manager can be accessed through the web by typing in the IP address of system that the manager was installed on into the search bar '''(https://<manager ip>)'''. Once that is done, you will be taken to the manager page and type in the user name and password, then all of the information on the systems added can be viewed.

'''Wazuh Agent''' '''Windows Configuration'''

* Get Wazuh running on a computer that already has it installed
# Open command prompt ('''admin''')
# Run the command below
# <code>'''"C:\Program Files (x86)\ossec-agent\agent-auth.exe" -m 10.21.25.12 -P password'''</code>
# If this command worked you are done. If this command fails you need to remove the agent from the list.

* Get Wazuh running on a computer that does not have it installed

# In file explorer navigate to Cisco Curriculum in Midgard (Q:)
# Copy the Deployed Applications folder and paste it in C:
# Change the folder name to DeployedApplications
#Run Windows PowerShell as '''ADMIN'''
# Enter: <code>'''cd c:\DeployedApplications'''</code>
# Enter the command: <code>'''.\wazuh-agent-4.2.5-1.msi /q WAZUH_MANAGER="10.21.25.12" WAZUH_REGISTRATION_SERVER="10.21.25.12" WAZUH_REGISTRATION_PASSWORD="password"'''</code>
'''Wazuh Agent''' '''Mac Configuration'''

* Log in to the computer with the '''24pintech''' account. You may also open this wiki page on that computer to copy and paste commands.

* Open a terminal window and install Wazuh agent using this command: <code>'''curl -so wazuh-agent-4.3.9.pkg <nowiki>https://packages.wazuh.com/4.x/macos/wazuh-agent-4.3.9-1.pkg</nowiki> && sudo launchctl setenv WAZUH_MANAGER '10.21.25.12' && sudo installer -pkg ./wazuh-agent-4.3.9.pkg -target /'''</code> (If prompted, use the 24pintech account password to finish the installation)
* Run this command to start Wazuh: '''<code>sudo /Library/Ossec/bin/wazuh-control start</code>'''
* Verify that the agent has been added in wazuh after refreshing the page.

[[File:Image.png|thumb|This is the menu, also known as the agent manager that opens when you insert <code>'''/var/ossec/bin/manage_agents'''</code>]]
'''Wazuh Agent Manager'''

Running this command will open the menu to add, remove, and edit agents (see picture on the right)

<code>'''/var/ossec/bin/manage_agents'''</code>

* '''Add an agent (A)'''
By entering "A" you can add an agent to the list. All you need is to input the name of the computer you want to add and the computers IP address.
* '''Extract key for an agent (E)'''
By entering "E" you can get a new key for an agent. All you need is to input the ID number of the agent. This can be done to help get a new key however this is likely unnecessary as you just need to run one command from command prompt on the agent you are trying to give a key to. (See "'''Wazuh Agent Windows Configuration'''")
* '''List already added agents (L)'''
By entering "L" you can view a list of every agent and that agents ID number. This can also be viewed from the Wazuh manager page in more detail however this is often a very convenient command when you need to check the list for one agent.
* '''Remove an agent (R)'''
By entering "R" you can remove an agent from the manager by entering the agents ID number. This is useful to remove agents we do not need or to remove faulty agents to fix them and get them running properly.

* '''Quit (Q)'''

By entering "Q" you can close the menu and return to the normal terminal screen.

== Monitoring Wazuh ==

===How to Monitor===
There is a lot of information present on the manager page with details on everything connected. Mainly, all the information that will want to be looked at is present on the Security Events, Integrity Monitoring, Agents, and Manager tabs for the information that we will be troubleshooting and coming up with solutions for. The main thing that will need to be looked for are going to be any failures seen on one of the servers or workstations. You will also want to look at the agents connected to see if things are in order or not with connection to the manager. Another thing would be vulnerabilities detected by the manager within our systems and note what kind of vulnerability that it is. The processes being made will also be something that needs to be monitored for any issues on the systems.
===What to look for===
====='''Modules'''=====
*
'''Security information management'''
*Security Events
**Alerts - This will be the main place to look for all of the systems current events taking place as far back as you need to. This will go over any login failures, malware, or anything of that nature will be viewed here across all agents. The key to looking at this all is section through the level of alert going from 1 - 12 with each increase in level being a higher alert that needs to be looked at. Anything above 7 will typically be what is unwanted unless another technician is performing a task that is causing said alerts. Take the proper steps as listed within the policy when any alert is worth being taken to the higher ups for proper handling.
'''Auditing and Policy Monitoring'''
*Security Configuration Assessments
**Here will be the most important place to look as you will need to monitor for any faults detected in the system's security. One of each device (All servers need to be checked) and then you as a tech will need to research into the issue if it is important. If there is a major security issue then this can be dealt with either by informing a higher up and getting the all clear to fix it, or if you are already in charge of fixing the security of the systems.
====='''''Management'''''=====
'''Administration'''
*This will probably be the most unused section of the SIEM, but if multiple technicians ever take it on then here is where all accounts would be managed depending on the trust within that technician, so restrictions can be set to ensure that all users have the correct access on the server, ensuring that nothing will be used against policy. This is also where rules will be configured for the nodes and clusters mainly for what will be showed on the virtual machine
'''Status and Reports'''
*This is where you will be able to generate a status report of the SIEM as well as seeing the status of each manager/cluster. By generating a report you will be given a detailed pdf of everything that has been logged for when you set it and you will be able to go over it and see anything that sticks out instead of having to check each individual module on the SIEM. You will also view the cluster health by seeing if one of the nodes has gone down and needs to be repaired to get it in working order once more.
====='''Agent'''=====
*Any and all issues that are had within the agent monitoring page can be checked for in the troubleshooting section of the [[SIEM: Configuration|SIEM: Configuration wiki page]].
'''Active'''
*Here you will be looking for any and all agents connected to the SIEM. You will look here for any newly added agents that are supposed to be there as well as if they have properly connected.
'''Disconnected'''
*You will look here to see if any important agents such as the servers are disconnected due to it being turned off or if it has been inactive for quite a while as they may need to be reset which can be done in many ways.
'''Never connected'''
*This will be used to check for any agents that have been connected improperly due to human error or any oversight that had happened during the configuration. If this happens to occur then some of the issues with the setup of an agent should be able to be fixed by viewing previous troubleshooting, but if the issue is unknown, then consult either the Wazuh documentation or a manager.
===Reporting===
[[File:Email.png|thumb|Config for email|294x294px]][[File:Report.png|thumb|Config for reports|277x277px]]Reports from the manager can be set up to email the information directly to us. In order to do this the '''Ossec.conf file''' needs to be edited to set up automatic reports by using the command With this you can choose who will receive it, the frequency of emails, and the level of alert it will send an email for once your information is filled into the box. Once you have made it in there will be a section to input a sending email and the recipient email, whatever your purpose is for receiving the email will most likely be for the higher alerts that need fixing immediately.

This is the command needed to access the ossec.conf file on the virtual machine.

<code>sudo nano /var/ossec/etc/ossec.conf</code>

'''''Warning: Configuring the Ossec.Conf file on either of the nodes or the server web page can lead to the server malfunctioning. Make sure you know exactly what you are doing and/or you have a backup ready before changing anything.'''''

== Wazuh Commands: ==

====Agent Config (Agent Side)====

* <code>'''net stop wazuh'''</code>
** Stops Wazuh
* <code>'''net start wazuh'''</code>
** Starts Wazuh
* <code>'''Restart-Service -Name wazuh'''</code>
*<code>'''systemctl restart wazuh-manager'''</code>
** Restarts Wazuh manager
* <code>'''"C:\Program Files (x86)\ossec-agent\agent-auth.exe" -m 10.21.25.12 -P password'''</code>
** Obtains a new key and activates an agent
==== Agent Config (Server Side)====

* <code>'''/var/ossec/bin/manage_agents'''</code>
** Opens agent manager. More info on the manager under "'''Wazuh Agent Manager'''"

====Server Config - Nano====

* <code>'''systemctl start/status/stop/restart wazuh-manager'''</code>
* <code>'''/usr/share/kibana/data/wazuh/config/wazuh.yml'''</code>
* <code>'''/var/ossec/etc/shared/dbms/agent.conf'''</code>
* <code>'''/var/ossec/etc/ossec.conf'''</code>
* <code>'''/etc/filebeat/filebeat.yml'''</code>
* <code>'''/etc/kibana/kibana.yml'''</code>
* <code>'''/var/ossec/bin/wazuh-control -j info'''</code>
* <code>'''/var/ossec/logs/active-responses.log'''</code>

Wazuh

2022-11-18T14:48:31Z

Kwalters:

Wazuh is the SIEM software that is used to make sure that all of our computers are up to standard in terms of system health and to monitor any security events. The Wazuh server lives on Valhalla in an Ubuntu virtual machine named Gustavo. There are also agents that are deployed onto each device which collect necessary information that will be needed to make a full report on any issues that may be occurring on said system. All of the data is then processed and sent to the manager which takes all of the data and organizes it into one source. It also utilizes Elasticstack which visualizes all of the data the manager has so that everything going on in 24Pintech's systems can be monitored without much hassle.

ㅤ

== Configuring Wazuh ==

=== Installation Process===
===='''Wazuh Manager''' ====
The manger can either be installed as a all in-one or distributed deployment. The deployment that has been used is all in-one which has all of the components of Wazuh installed onto the server, Gustavo, through Ubuntu. You can install the manager using the process at https://documentation.wazuh.com/4.2/installation-guide/open-distro/all-in-one-deployment/all-in-one.html for APT. Once installed, the manager can be accessed the web by typing in the IP address of system that the manager was installed on into the search bar '''(https://<manager ip>)'''. Once that is done, you will be taken to the manager page and type in the user name and password, then all of the information on the systems added can be viewed.

'''Wazuh Agent''' '''Windows Configuration'''

* Get Wazuh running on a computer that already has it installed
# Open command prompt ('''admin''')
# Run the command below
# <code>'''"C:\Program Files (x86)\ossec-agent\agent-auth.exe" -m 10.21.25.12 -P password'''</code>
# If this command worked you are done. If this command fails you need to remove the agent from the list.

* Get Wazuh running on a computer that does not have it installed

# In file explorer navigate to Cisco Curriculum in Midgard (Q:)
# Copy the Deployed Applications folder and paste it in C:
# Change the folder name to DeployedApplications
#Run Windows PowerShell as '''ADMIN'''
# Enter: <code>'''cd c:\DeployedApplications'''</code>
# Enter the command: <code>'''.\wazuh-agent-4.2.5-1.msi /q WAZUH_MANAGER="10.21.25.12" WAZUH_REGISTRATION_SERVER="10.21.25.12" WAZUH_REGISTRATION_PASSWORD="password"'''</code>
'''Wazuh Agent''' '''Mac Configuration'''

* Log in to the computer with the '''24pintech''' account. You may also open this wiki page on that computer to copy and paste commands.

* Open a terminal window and install Wazuh agent using this command: <code>'''curl -so wazuh-agent-4.3.9.pkg <nowiki>https://packages.wazuh.com/4.x/macos/wazuh-agent-4.3.9-1.pkg</nowiki> && sudo launchctl setenv WAZUH_MANAGER '10.21.25.12' && sudo installer -pkg ./wazuh-agent-4.3.9.pkg -target /'''</code> (If prompted, use the 24pintech account password to finish the installation)
* Run this command to start Wazuh: '''<code>sudo /Library/Ossec/bin/wazuh-control start</code>'''
* Verify that the agent has been added in wazuh after refreshing the page.

[[File:Image.png|thumb|This is the menu, also known as the agent manager that opens when you insert <code>'''/var/ossec/bin/manage_agents'''</code>]]
'''Wazuh Agent Manager'''

Running this command will open the menu to add, remove, and edit agents (see picture on the right)

<code>'''/var/ossec/bin/manage_agents'''</code>

* '''Add an agent (A)'''
By entering "A" you can add an agent to the list. All you need is to input the name of the computer you want to add and the computers IP address.
* '''Extract key for an agent (E)'''
By entering "E" you can get a new key for an agent. All you need is to input the ID number of the agent. This can be done to help get a new key however this is likely unnecessary as you just need to run one command from command prompt on the agent you are trying to give a key to. (See "'''Wazuh Agent Windows Configuration'''")
* '''List already added agents (L)'''
By entering "L" you can view a list of every agent and that agents ID number. This can also be viewed from the Wazuh manager page in more detail however this is often a very convenient command when you need to check the list for one agent.
* '''Remove an agent (R)'''
By entering "R" you can remove an agent from the manager by entering the agents ID number. This is useful to remove agents we do not need or to remove faulty agents to fix them and get them running properly.

* '''Quit (Q)'''

By entering "Q" you can close the menu and return to the normal terminal screen.

== Monitoring Wazuh ==

===How to Monitor===
There is a lot of information present on the manager page with details on everything connected. Mainly, all the information that will want to be looked at is present on the Security Events, Integrity Monitoring, Agents, and Manager tabs for the information that we will be troubleshooting and coming up with solutions for. The main thing that will need to be looked for are going to be any failures seen on one of the servers or workstations. You will also want to look at the agents connected to see if things are in order or not with connection to the manager. Another thing would be vulnerabilities detected by the manager within our systems and note what kind of vulnerability that it is. The processes being made will also be something that needs to be monitored for any issues on the systems.
===What to look for===
====='''Modules'''=====
*
'''Security information management'''
*Security Events
**Alerts - This will be the main place to look for all of the systems current events taking place as far back as you need to. This will go over any login failures, malware, or anything of that nature will be viewed here across all agents. The key to looking at this all is section through the level of alert going from 1 - 12 with each increase in level being a higher alert that needs to be looked at. Anything above 7 will typically be what is unwanted unless another technician is performing a task that is causing said alerts. Take the proper steps as listed within the policy when any alert is worth being taken to the higher ups for proper handling.
'''Auditing and Policy Monitoring'''
*Security Configuration Assessments
**Here will be the most important place to look as you will need to monitor for any faults detected in the system's security. One of each device (All servers need to be checked) and then you as a tech will need to research into the issue if it is important. If there is a major security issue then this can be dealt with either by informing a higher up and getting the all clear to fix it, or if you are already in charge of fixing the security of the systems.
====='''''Management'''''=====
'''Administration'''
*This will probably be the most unused section of the SIEM, but if multiple technicians ever take it on then here is where all accounts would be managed depending on the trust within that technician, so restrictions can be set to ensure that all users have the correct access on the server, ensuring that nothing will be used against policy. This is also where rules will be configured for the nodes and clusters mainly for what will be showed on the virtual machine
'''Status and Reports'''
*This is where you will be able to generate a status report of the SIEM as well as seeing the status of each manager/cluster. By generating a report you will be given a detailed pdf of everything that has been logged for when you set it and you will be able to go over it and see anything that sticks out instead of having to check each individual module on the SIEM. You will also view the cluster health by seeing if one of the nodes has gone down and needs to be repaired to get it in working order once more.
====='''Agent'''=====
*Any and all issues that are had within the agent monitoring page can be checked for in the troubleshooting section of the [[SIEM: Configuration|SIEM: Configuration wiki page]].
'''Active'''
*Here you will be looking for any and all agents connected to the SIEM. You will look here for any newly added agents that are supposed to be there as well as if they have properly connected.
'''Disconnected'''
*You will look here to see if any important agents such as the servers are disconnected due to it being turned off or if it has been inactive for quite a while as they may need to be reset which can be done in many ways.
'''Never connected'''
*This will be used to check for any agents that have been connected improperly due to human error or any oversight that had happened during the configuration. If this happens to occur then some of the issues with the setup of an agent should be able to be fixed by viewing previous troubleshooting, but if the issue is unknown, then consult either the Wazuh documentation or a manager.
===Reporting===
[[File:Email.png|thumb|Config for email|294x294px]][[File:Report.png|thumb|Config for reports|277x277px]]Reports from the manager can be set up to email the information directly to us. In order to do this the '''Ossec.conf file''' needs to be edited to set up automatic reports by using the command With this you can choose who will receive it, the frequency of emails, and the level of alert it will send an email for once your information is filled into the box. Once you have made it in there will be a section to input a sending email and the recipient email, whatever your purpose is for receiving the email will most likely be for the higher alerts that need fixing immediately.

This is the command needed to access the ossec.conf file on the virtual machine.

<code>sudo nano /var/ossec/etc/ossec.conf</code>

'''''Warning: Configuring the Ossec.Conf file on either of the nodes or the server web page can lead to the server malfunctioning. Make sure you know exactly what you are doing and/or you have a backup ready before changing anything.'''''

== Wazuh Commands: ==

====Agent Config (Agent Side)====

* <code>'''net stop wazuh'''</code>
** Stops Wazuh
* <code>'''net start wazuh'''</code>
** Starts Wazuh
* <code>'''Restart-Service -Name wazuh'''</code>
*<code>'''systemctl restart wazuh-manager'''</code>
** Restarts Wazuh manager
* <code>'''"C:\Program Files (x86)\ossec-agent\agent-auth.exe" -m 10.21.25.12 -P password'''</code>
** Obtains a new key and activates an agent
==== Agent Config (Server Side)====

* <code>'''/var/ossec/bin/manage_agents'''</code>
** Opens agent manager. More info on the manager under "'''Wazuh Agent Manager'''"

====Server Config - Nano====

* <code>'''systemctl start/status/stop/restart wazuh-manager'''</code>
* <code>'''/usr/share/kibana/data/wazuh/config/wazuh.yml'''</code>
* <code>'''/var/ossec/etc/shared/dbms/agent.conf'''</code>
* <code>'''/var/ossec/etc/ossec.conf'''</code>
* <code>'''/etc/filebeat/filebeat.yml'''</code>
* <code>'''/etc/kibana/kibana.yml'''</code>
* <code>'''/var/ossec/bin/wazuh-control -j info'''</code>
* <code>'''/var/ossec/logs/active-responses.log'''</code>

ESXi

2022-11-09T18:11:27Z

Kwalters: /* Adding ESXi to the domain */

[[Category:VMware]]
==What is it==
[[File:VMwareESXiHostClientSummary.png|thumb|640x640px|General image of ESXi web interface|link=https://10.21.25.11//wiki.24pin.tech/File:VMwareESXiHostClientSummary.png]]ESXi is an OS designed to hold many virtual machines on one physical machine. It is identified as a type-1 hypervisor developed by VMware. We are using it currently for at least 4 of our machines in the classroom. Those machines are Heimdall, Thor, Asgard, and Valhalla. Heimdall and Thor are using the 6.7 license as explained in the Installation of ESXi heading. Asgard and Valhalla are using version 7.0+ which we paid for the licenses.
==Installation of ESXi==
The installation method of ESXi is pretty simple. All you will need is a computer/server and a flash drive. To be able to actually access the server you'll end up needing the machine to be connected to the internet. The procedure is as follows:

*Grab a image of ESXi from VMware's page. Depending on the importance or role of the server, you should use vSphere 6.7 for testing and small project purposes. Use 7.0+ as a limited resource since we only have so many activations available. You can grab all of our ISOs from the following directory on our domain, [https://10.21.25.11//wiki.24pin.tech/Mhs.24pin.tech mhs.24pin.tech], \\10.21.25.13/Cisco Curriculum/vSphere Downloads/ESXi ISOs/
*The rest of the installation process is pretty simple and can be found here: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-6FFA928F-7F7D-4B1A-B05C-777279233A77.html
*Once installed go to manage>licensing and input your license key, or you can use evaluation mode for up to at least 30 days. Though if you are using version 6.7 you can use the following key: 144AH-AU10P-W8888-0A22K-85912 and if you are going to use 7.0+ you can grab the product key from our vSphere Downloads folder from above.

==Management of a ESXi Machine's Local Interface==
[[File:VCenter interface.png|thumb|310x310px|link=https://10.21.25.11//wiki.24pin.tech/File:VCenter_interface.png]]After you install ESXi you should be greeted with a screen like shown to the right. (The screenshot is one of the vCenter server but a ESXi local interface should look similar)Through this screen you will be able to change management settings such as hostname, basic management networking, etc. A specific list of what you can do from the machine locally can be found below, to access these options you need to press f2 and use the login you created for the machine.

*Configure local password
*Configure lockdown
*Configure/Restart/Test Management Network and restore default networking settings
*Configure keyboard
*Troubleshooting Options
*View systems logs, support information
*Reset System Configurations

==Accessing ESXi's web interface==
To actually be able to get into ESXi you'll need to be able to access the server using a web interface. To get into the server simply put the ip address of the server into your web browser like this, [http://10.21.25.2/ http://10.21.25.2]. Once prompted to login, use the default username root and the root password you set during installation. You will be able to add the device to the domain and be able to create other users once logged in with root.
==Creating a VM==
Creating a VM on ESXi is pretty simple. The big thing is that you have to make sure your server/ESXi host has enough resources to share with it's VMs. You can create as many VMs as you want as long as you have the resources to see fit. Its best practice to try to limit your resources you give to a single machine to a minimum. For example, you won't be giving a domain controller tasked with basic tasks such as DNS, Active Directory, and DHCP 1 TB of storage and 32 logical cores. To determine the correct resources for your machine you'll want to research the best practices for that type of machine. The following is the steps of creating a virtual machine:[[File:Friia config.png|thumb|382x382px|Basic settings of Friia our secondary domain controller|link=https://10.21.25.11//wiki.24pin.tech/File:Friia_config.png]]

*Move into the Virtual Machines tab of ESXi as shown in the image at the top of the page.
*From there you will want to press create/register a VM
*You will be prompted with three options, to create a new VM, deploy a machine from OVF or OVA, or register a existing machine. For our purposes we will be creating a new VM.
*Next you will want to enter the name of the VM (this is only for the ESXi interface and has no effect on the VM itself) and choose what OS the VM will be. This is for management purposes.
*The next step asks you where you would like the machine to be actually located. This gets pretty in depth and lets you choose a storage point other than the local machine. Choosing a storage point other than the local machine is usually used when implanting redundancy. For our purposes we will be choosing the local storage.
*Now you actually get to assign the resources to your VM. You'll be able to set how many logical cores, ram, and storage the VM has. Once again do research on what the basic requirements of the VM you are creating. When choosing your networking settings use the machines default for now. This can get pretty in depth but once again we are staying basic here. Here you will also be able to choose the ISO file you are using to setup the machine. You simply want to choose it as a CD drive and upload the image either through the network or locally though a USB.
*That's it. Now you can go ahead and finalize the process of creating the VM.

==Adding ESXi to the domain==
Adding ESXi to the domain can easily be done by heading over to the manage tab on the left of the ESXi web interface. From there you will want to go into the Security & Users tab and down into Authentication. You should see something like this screenshot below. Here you will be able to press join domain. All you will have to do is enter the domain name, in our case mhs.24pin.tech and a admin login for that domain. If Domain Users are unable to login then leave the domain and rejoin.[[File:Asgard Domain.png|center|thumb|601x601px|link=https://10.21.25.11//wiki.24pin.tech/File:Asgard_Domain.png]]
==ESXi Networking==
===Brief Overview===
The ESXi machine basically has its own local environment built into it. Once you setup the machine and access the networking portion from the web interface you'll see that the machine has it's own vNICs, vSwitches, vVLANs, etc. If you want to get experienced with ESXi and know how to manage machines networking wise you'll need to know about these. A brief breakdown of this networking portion is that you'll have a VM Port group all assigned to a Virtual Switch which connects the VMs to the physical NICs. You can do many other things with this networking environment like making closed off test environments, separating VLANs, and configuring VMWare offered features like vMotion.
===Management===
When you initially setup the ESXi machine you create a management IP address. This is used to initially setup the machine and to access the web interface whenever you need it. You could also use the DNS name of the server once that is setup as well. If anything ever goes wrong on the networking side and you can't remotely access the server, you may need to go into the local server and reset the networking on the machine. This could be done easily with the following steps:

#Go into the local machine and press F2, it will ask for the root login that you created on initial setup.
#This interface is used to change anything management wise for the ESXi machine. (You can reset root password, reset networking, etc.)
#For our purpose we will go into the reset management network, what this will do is reset the NICs on the machine and VLANs that way it goes back to its original setup, this will usually fix networking issues.
#In this interface you can also edit the assigned VLAN, NIC teaming, etc. It is very helpful for troubleshooting.

===NIC Teaming===
Whenever you plug in a new cable to the physical machine it should automatically pick it up as a physical NIC and assign it a MAC address. To actually assign all the other cables other than the management cable to a interface on the machine you'll need to manually assign it to a Virtual Switch. After that you have to make and assign all the VMs to a port group and assign that port group to the switch that is connected to the NIC team. The process of creating a NIC team can be followed with this process:

#Open up the web interface for the ESXi machine. For my example I will be using Valhalla (10.21.25.2)
#Go to the networking portion of ESXi which can be found on the list of drop downs to the left.
#You'll see multiple tabs including Port Groups, Virtual Switches, Physical NICs, VMKernel NICs, TCP/IP Stacks, Firewall Rules. We can leave VMKernel, TCP/IP Stacks, and the Firewall alone for now.
#Go into the Physical NIC tab to verify that all of your NICs are activated and plugged in.
#Next you will want to create a new Virtual Switch (by switching to the Virtual Switch tab and pressing add new switch), name this something that you'll easily identify.
#Leave pretty much everything the same and click add.
#Once the virtual switch has been made you'll want to click create new uplink, these are the physical NICs and assigns them to the virtual switch.
#After assigning the uplinks go into the settings of the switch to verify that they are assigned. You can leave the rest of the settings the same, or change them depending on your purposes or knowledge.
#Now go into the Port Group tab. You can either use the default Port Group (recommended if you already have VMs running on the machine) or create a new one with your own name. If you do use the default Port Group you will have to go into the settings of it and assign it to the new vSwitch. These are what you will assign the VMs to so that they are connected.
#Once done you should verify all the connections of the VMs and make sure they are all connected to the correct Port Group. Ta-da you are done.

==Moving a pre existing machine to or from ESXi==
[[File:Word-image-51.png|thumb|442x442px|Starwind converter|link=https://10.21.25.11//wiki.24pin.tech/File:Word-image-51.png]]The process of moving pre existing machines onto ESXi and copying them off is pretty easy. You can do this by using [https://10.21.25.11//wiki.24pin.tech/Starwind Starwind]. [https://10.21.25.11//wiki.24pin.tech/Starwind Starwind] will allow you to choose a remote image, local file, or physical machine and put that image onto another machine locally or as a VM. It became pretty helpful in our process of virtualizing all of our physical servers onto one machine.

Another way of doing this could be through vMotion. This moves a VM from one vSphere machine to another while keeping the VM running and functional. Though to set this up you will need to assign a new vNIC to each machine the destination and source and that will require a IP address from our domain.
==Probable Issues==

*One day a cable came slightly unplugged and the domain controllers started acting up. The web server also had some issues. We don't know if this was the

==Helpful Links==
For those that would like more information than what I can provide:

*https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/virtual_networking_concepts.pdf #General piece on VMWare Virtual Networking, a bit dated
*https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-B57FBE96-21EA-401C-BAA6-BDE88108E4BB.html #Best practices, should probably follow
*https://www.youtube.com/watch?v=GkC6lLfVj50 Creating a mac VM

DHCP

2022-11-08T20:21:17Z

Kwalters:

[[Category:Windows]]
=Our DHCP Setup=

Our DHCP is run on [[Odin]] and [[Friia]]. DHCP is what gives out the IP addresses to the devices on our network. Without it, we would have to use static IP addresses, or we would not be able to communicate properly. Both of the servers keep each other synced on what IP addresses have been given out to ensure there are no conflicts.

==Address Pool==

Our scope is 10.21.25.0, as that is our network. The DHCP server only distributes addresses in from 10.21.25.30 to 10.21.25.247. The rest in the network are reserved for servers and printers, or anything else that needs a static IP. The following chart represents our current setup...
{| class="wikitable"
|+Reservations
!Hostname
!IP Address
|-
|Gateway
|10.21.25.1
|-
|Valhalla
|10.21.25.2
|-
|Fenrir
|10.21.25.3
|-
|Friia
|10.21.25.4
|-
|Yggdrasil
|10.21.25.5
|-
|Sakaar
|10.21.25.6
|-
|Asgard
|10.21.25.7
|-
|Heimdall
|10.21.25.8
|-
|Xandar
|10.21.25.9
|-
|
|10.21.25.10
|-
|Logan
|10.21.25.11
|-
|Sleipnir
|10.21.25.12
|-
|Midgard
|10.21.25.13
|-
|
|10.21.25.14
|-
|
|10.21.25.15
|-
|
|10.21.25.16
|-
|IOlan
|10.21.25.17
|-
|OpenGear
|10.21.25.18
|-
|
|10.21.25.19
|-
|vMotion (Val)
|10.21.25.20
|-
|
|10.21.25.21
|-
|vMotion (Asg)
|10.21.25.22
|-
|
|10.21.25.23
|-
|
|10.21.25.24
|-
|
|10.21.25.25
|-
|vSphere Rep
|10.21.25.26
|-
|
|10.21.25.27
|-
|Datacenter Switch
|10.21.25.28
|-
|FOG
|10.21.25.29
|-
|3D Print
|10.21.25.129
|-
|LaserPrint
|10.21.25.241
|-
|LaserColorPrint
|10.21.25.243
|}

==Address Leases==

These are all of the current DHCP releases that the DHCP servers have put out that are active.

==Reservations==

This is where all of our static DHCP-side reservations for our servers, printers, NAS, etc., are located. You can double click any of them to edit their specific settings.

==='''Hostname IP address'''===
LoganWeb (VM on Valhalla) 10.21.25.11

NAS 24PinTech 10.21.25.16

SC-P8000Series-2D6580 10.21.25.90

NPI7C274C (HP LaserJet P4014) 10.21.25.241

NPI82FF0E (HP Color LaserJet M553) 10.21.25.243

==Scope Options==

This is where we configure our DHCP options. To configure options that we don't already have set, right click "Scope Options" and click on "Configure Options" and configure what you need. Below are the options we already have set:

[[File:DHCP_Options.PNG]]

These options set where the computers will look for DNS, what our domain name is ([[CISCOACA.local]]) and the other options tell computers to PXE boot from [[FOG]] and configures the settings they need to boot from [[FOG]].

==Policies==

These are settings that are applied to certain devices based off of rules defined by the policy, like IP address range, vendor, etc.

The only policy we have currently configured is called UEFI, which applies to network booting via UEFI. It sets options 66 and 67 to make sure devices will boot properly off of [[FOG]]. 67 is set to ipxe.efi, and 66 is set to 10.21.25.4.

==Server Options==

This is where settings can be configured globally across the whole DHCP server. We have none of these currently configured.

==Policies (Not within scope)==

Same as above policies but global, we do not have this configured.

==Filters==

This allows you to block or allow certain MAC addresses from receiving DHCP addresses.

Proxmox

2022-10-25T19:50:06Z

Kwalters: Created page with "Proxmox"

Proxmox

DHCP

2022-10-24T20:09:47Z

Kwalters:

[[Category:Windows]]
=Our DHCP Setup=

Our DHCP is run on [[Odin]] and [[Friia]]. DHCP is what gives out the IP addresses to the devices on our network. Without it, we would have to use static IP addresses, or we would not be able to communicate properly. Both of the servers keep each other synced on what IP addresses have been given out to ensure there are no conflicts.

==Address Pool==

Our scope is 10.21.25.0, as that is our network. The DHCP server only distributes addresses in from 10.21.25.30 to 10.21.25.247. The rest in the network are reserved for servers and printers, or anything else that needs a static IP. The following chart represents our current setup...
{| class="wikitable"
|+Reservations
!Hostname
!IP Address
|-
|Gateway
|10.21.25.1
|-
|Valhalla
|10.21.25.2
|-
|Fenrir
|10.21.25.3
|-
|Friia
|10.21.25.4
|-
|Yggdrasil
|10.21.25.5
|-
|Sakaar
|10.21.25.6
|-
|Asgard
|10.21.25.7
|-
|Heimdall
|10.21.25.8
|-
|Xandar
|10.21.25.9
|-
|
|10.21.25.10
|-
|Logan
|10.21.25.11
|-
|Sleipnir
|10.21.25.12
|-
|Midgard
|10.21.25.13
|-
|
|10.21.25.14
|-
|
|10.21.25.15
|-
|
|10.21.25.16
|-
|IOlan
|10.21.25.17
|-
|OpenGear
|10.21.25.18
|-
|
|10.21.25.19
|-
|vMotion (Val)
|10.21.25.20
|-
|
|10.21.25.21
|-
|vMotion (Asg)
|10.21.25.22
|-
|
|10.21.25.23
|-
|
|10.21.25.24
|-
|
|10.21.25.25
|-
|vSphere Rep
|10.21.25.26
|-
|
|10.21.25.27
|-
|
|10.21.25.28
|-
|FOG
|10.21.25.29
|-
|
|10.21.25.30
|-
|3D Print
|10.21.25.129
|-
|LaserPrint
|10.21.25.241
|-
|LaserColorPrint
|10.21.25.243
|}

==Address Leases==

These are all of the current DHCP releases that the DHCP servers have put out that are active.

==Reservations==

This is where all of our static DHCP-side reservations for our servers, printers, NAS, etc., are located. You can double click any of them to edit their specific settings.

==='''Hostname IP address'''===
LoganWeb (VM on Valhalla) 10.21.25.11

NAS 24PinTech 10.21.25.16

SC-P8000Series-2D6580 10.21.25.90

NPI7C274C (HP LaserJet P4014) 10.21.25.241

NPI82FF0E (HP Color LaserJet M553) 10.21.25.243

==Scope Options==

This is where we configure our DHCP options. To configure options that we don't already have set, right click "Scope Options" and click on "Configure Options" and configure what you need. Below are the options we already have set:

[[File:DHCP_Options.PNG]]

These options set where the computers will look for DNS, what our domain name is ([[CISCOACA.local]]) and the other options tell computers to PXE boot from [[FOG]] and configures the settings they need to boot from [[FOG]].

==Policies==

These are settings that are applied to certain devices based off of rules defined by the policy, like IP address range, vendor, etc.

The only policy we have currently configured is called UEFI, which applies to network booting via UEFI. It sets options 66 and 67 to make sure devices will boot properly off of [[FOG]]. 67 is set to ipxe.efi, and 66 is set to 10.21.25.4.

==Server Options==

This is where settings can be configured globally across the whole DHCP server. We have none of these currently configured.

==Policies (Not within scope)==

Same as above policies but global, we do not have this configured.

==Filters==

This allows you to block or allow certain MAC addresses from receiving DHCP addresses.

DHCP

2022-10-19T18:28:34Z

Kwalters:

[[Category:Windows]]
=Our DHCP Setup=

Our DHCP is run on [[Odin]] and [[Friia]]. DHCP is what gives out the IP addresses to the devices on our network. Without it, we would have to use static IP addresses, or we would not be able to communicate properly. Both of the servers keep each other synced on what IP addresses have been given out to ensure there are no conflicts.

==Address Pool==

Our scope is 10.21.25.0, as that is our network. The DHCP server only distributes addresses in from 10.21.25.30 to 10.21.25.247. The rest in the network are reserved for servers and printers, or anything else that needs a static IP. The following chart represents our current setup...
{| class="wikitable"
|+Reservations
!Hostname
!IP Address
|-
|Gateway
|10.21.25.1
|-
|Valhalla
|10.21.25.2
|-
|Fenrir
|10.21.25.3
|-
|Friia
|10.21.25.4
|-
|Yggdrasil
|10.21.25.5
|-
|Sakaar
|10.21.25.6
|-
|Asgard
|10.21.25.7
|-
|Heimdall
|10.21.25.8
|-
|
|10.21.25.9
|-
|
|10.21.25.10
|-
|Logan
|10.21.25.11
|-
|Sleipnir
|10.21.25.12
|-
|Midgard
|10.21.25.13
|-
|
|10.21.25.14
|-
|
|10.21.25.15
|-
|
|10.21.25.16
|-
|IOlan
|10.21.25.17
|-
|OpenGear
|10.21.25.18
|-
|
|10.21.25.19
|-
|vMotion (Val)
|10.21.25.20
|-
|
|10.21.25.21
|-
|vMotion (Asg)
|10.21.25.22
|-
|
|10.21.25.23
|-
|
|10.21.25.24
|-
|
|10.21.25.25
|-
|vSphere Rep
|10.21.25.26
|-
|
|10.21.25.27
|-
|
|10.21.25.28
|-
|FOG
|10.21.25.29
|-
|
|10.21.25.30
|-
|3D Print
|10.21.25.129
|-
|LaserPrint
|10.21.25.241
|-
|LaserColorPrint
|10.21.25.243
|}

==Address Leases==

These are all of the current DHCP releases that the DHCP servers have put out that are active.

==Reservations==

This is where all of our static DHCP-side reservations for our servers, printers, NAS, etc., are located. You can double click any of them to edit their specific settings.

==='''Hostname IP address'''===
LoganWeb (VM on Valhalla) 10.21.25.11

NAS 24PinTech 10.21.25.16

SC-P8000Series-2D6580 10.21.25.90

NPI7C274C (HP LaserJet P4014) 10.21.25.241

NPI82FF0E (HP Color LaserJet M553) 10.21.25.243

==Scope Options==

This is where we configure our DHCP options. To configure options that we don't already have set, right click "Scope Options" and click on "Configure Options" and configure what you need. Below are the options we already have set:

[[File:DHCP_Options.PNG]]

These options set where the computers will look for DNS, what our domain name is ([[CISCOACA.local]]) and the other options tell computers to PXE boot from [[FOG]] and configures the settings they need to boot from [[FOG]].

==Policies==

These are settings that are applied to certain devices based off of rules defined by the policy, like IP address range, vendor, etc.

The only policy we have currently configured is called UEFI, which applies to network booting via UEFI. It sets options 66 and 67 to make sure devices will boot properly off of [[FOG]]. 67 is set to ipxe.efi, and 66 is set to 10.21.25.4.

==Server Options==

This is where settings can be configured globally across the whole DHCP server. We have none of these currently configured.

==Policies (Not within scope)==

Same as above policies but global, we do not have this configured.

==Filters==

This allows you to block or allow certain MAC addresses from receiving DHCP addresses.

VSphere

2022-10-14T20:30:22Z

Kwalters: /* Installation */

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplicationAsgard

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configuration] for the machine and then deploy the OVF.
*Once the machine boots up and says you can [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configure] it from the web interface go ahead and do so (login should be root and the password you set)
*When finished, go to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2022-10-14T20:27:36Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplicationAsgard

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configuration] for the machine.

*Once you confirm, the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can [https://docs.google.com/document/d/1e8npMreQRZdTKqSKoV2T3RAA2wlfOhAdkdSOxdIBvOk/edit?usp=sharing configure] it from the web interface go ahead and do so. The login should be root and the password you set.
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2022-10-14T20:22:44Z

Kwalters: /* vMotion */

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== Migrating a VM (vMotion) ===
vMotion is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplicationAsgard

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the configuration for the machine using the following:
*# Password - (Your Choice)
*# NTP Server - 10.21.25.3
*# Hostname - vSphereReplicationAsgard
*# Default Gateway - 10.21.25.1
*# Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
*# Domain Name Servers - 10.21.25.3
*# Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
*# Management Network Netmask - 255.255.255.0

*Once you confirm the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface confirm that everything is set to the following
*VR>Configuration:
*#Hostname - vSphereReplicationAsgard.mhs.24pin.tech
*#Preferred DNS Server - 10.21.25.3
*#Alternate DNS Server - 10.21.25.4
*#Domain search path - Yggdrasil.mhs.24pin.tech
*#IPv4 Default Gateway - 10.21.25.1
*#IPv4 Address - 10.21.25.26
*#Netmask - 255.255.255.0
*Network>Address:
*#LookupService Address - yggdrasil.mhs.24pin.tech
*#VRM Host - 10.21.25.26
*#VRM Site Name - vSphereReplicationAsgard
*#vCenter Server Address - Yggdrasil.mhs.24pin.tech
*#vCenter Server Port - 80
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2022-10-14T20:21:32Z

Kwalters: /* vSphere Replication */

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on.

=== vMotion ===
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

==== Migrating ====
* Find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

===Snapshots===
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

==== Creation ====

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplicationAsgard

==== Reverting ====
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the configuration for the machine using the following:
*# Password - (Your Choice)
*# NTP Server - 10.21.25.3
*# Hostname - vSphereReplicationAsgard
*# Default Gateway - 10.21.25.1
*# Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
*# Domain Name Servers - 10.21.25.3
*# Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
*# Management Network Netmask - 255.255.255.0

*Once you confirm the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface confirm that everything is set to the following
*VR>Configuration:
*#Hostname - vSphereReplicationAsgard.mhs.24pin.tech
*#Preferred DNS Server - 10.21.25.3
*#Alternate DNS Server - 10.21.25.4
*#Domain search path - Yggdrasil.mhs.24pin.tech
*#IPv4 Default Gateway - 10.21.25.1
*#IPv4 Address - 10.21.25.26
*#Netmask - 255.255.255.0
*Network>Address:
*#LookupService Address - yggdrasil.mhs.24pin.tech
*#VRM Host - 10.21.25.26
*#VRM Site Name - vSphereReplicationAsgard
*#vCenter Server Address - Yggdrasil.mhs.24pin.tech
*#vCenter Server Port - 80
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2022-10-14T20:18:07Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.

== Virtual Machines ==

=== Creating a VM ===
Right click on one of the hosts and press new virtual machine to begin creating a new virtual machine:

* Select how you want to create a virtual machine. Typically we will use the first option of creating a new virtual machine.
* Give the VM a name and then select the host that you want to put the VM on.
* Select the default storage that shows up (either ValhallaLocal or AsgardLocal)
* Select the operating system that you wish to use and then pick the version.
* Choose the amount of cpus, memory, and and storage that you will need to use for the virtual machine.
* To install the operating system you also need to pick Datastore ISO File in CD/DVD Drive and check connect at power on

==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the configuration for the machine using the following:
*# Password - (Your Choice)
*# NTP Server - 10.21.25.3
*# Hostname - vSphereReplicationAsgard
*# Default Gateway - 10.21.25.1
*# Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
*# Domain Name Servers - 10.21.25.3
*# Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
*# Management Network Netmask - 255.255.255.0

*Once you confirm the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface confirm that everything is set to the following
*VR>Configuration:
*#Hostname - vSphereReplicationAsgard.mhs.24pin.tech
*#Preferred DNS Server - 10.21.25.3
*#Alternate DNS Server - 10.21.25.4
*#Domain search path - Yggdrasil.mhs.24pin.tech
*#IPv4 Default Gateway - 10.21.25.1
*#IPv4 Address - 10.21.25.26
*#Netmask - 255.255.255.0
*Network>Address:
*#LookupService Address - yggdrasil.mhs.24pin.tech
*#VRM Host - 10.21.25.26
*#VRM Site Name - vSphereReplicationAsgard
*#vCenter Server Address - Yggdrasil.mhs.24pin.tech
*#vCenter Server Port - 80
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Migrating ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

=== Creation ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplicationAsgard

=== Reverting ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2022-10-14T20:02:56Z

Kwalters: /* Restoring */

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the configuration for the machine using the following:
*# Password - (Your Choice)
*# NTP Server - 10.21.25.3
*# Hostname - vSphereReplicationAsgard
*# Default Gateway - 10.21.25.1
*# Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
*# Domain Name Servers - 10.21.25.3
*# Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
*# Management Network Netmask - 255.255.255.0

*Once you confirm the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface confirm that everything is set to the following
*VR>Configuration:
*#Hostname - vSphereReplicationAsgard.mhs.24pin.tech
*#Preferred DNS Server - 10.21.25.3
*#Alternate DNS Server - 10.21.25.4
*#Domain search path - Yggdrasil.mhs.24pin.tech
*#IPv4 Default Gateway - 10.21.25.1
*#IPv4 Address - 10.21.25.26
*#Netmask - 255.255.255.0
*Network>Address:
*#LookupService Address - yggdrasil.mhs.24pin.tech
*#VRM Host - 10.21.25.26
*#VRM Site Name - vSphereReplicationAsgard
*#vCenter Server Address - Yggdrasil.mhs.24pin.tech
*#vCenter Server Port - 80
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing recovery options you want to use the latest available data if it is a restoration of a broken machine and make sure the machine doesn’t turn on at start.
*For the machine you want to choose the opposite of what the current machine is on (for example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*Be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Migrating ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM. Snapshots should be created at least once a month or before any major updates/changes to a machine.

=== Creation ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplicationAsgard

=== Reverting ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2022-10-14T19:58:17Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the highest level password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the configuration for the machine using the following:
*# Password - (Your Choice)
*# NTP Server - 10.21.25.3
*# Hostname - vSphereReplicationAsgard
*# Default Gateway - 10.21.25.1
*# Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
*# Domain Name Servers - 10.21.25.3
*# Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
*# Management Network Netmask - 255.255.255.0

*Once you confirm the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface confirm that everything is set to the following
*VR>Configuration:
*#Hostname - vSphereReplicationAsgard.mhs.24pin.tech
*#Preferred DNS Server - 10.21.25.3
*#Alternate DNS Server - 10.21.25.4
*#Domain search path - Yggdrasil.mhs.24pin.tech
*#IPv4 Default Gateway - 10.21.25.1
*#IPv4 Address - 10.21.25.26
*#Netmask - 255.255.255.0
*Network>Address:
*#LookupService Address - yggdrasil.mhs.24pin.tech
*#VRM Host - 10.21.25.26
*#VRM Site Name - vSphereReplicationAsgard
*#vCenter Server Address - Yggdrasil.mhs.24pin.tech
*#vCenter Server Port - 80
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Migrating ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2022-10-13T20:35:01Z

Kwalters: /* Installing */

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* Run the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the ITX password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the configuration for the machine using the following:
*# Password - (Your Choice)
*# NTP Server - 10.21.25.3
*# Hostname - vSphereReplicationAsgard
*# Default Gateway - 10.21.25.1
*# Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
*# Domain Name Servers - 10.21.25.3
*# Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
*# Management Network Netmask - 255.255.255.0

*Once you confirm the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface confirm that everything is set to the following
*VR>Configuration:
*#Hostname - vSphereReplicationAsgard.mhs.24pin.tech
*#Preferred DNS Server - 10.21.25.3
*#Alternate DNS Server - 10.21.25.4
*#Domain search path - Yggdrasil.mhs.24pin.tech
*#IPv4 Default Gateway - 10.21.25.1
*#IPv4 Address - 10.21.25.26
*#Netmask - 255.255.255.0
*Network>Address:
*#LookupService Address - yggdrasil.mhs.24pin.tech
*#VRM Host - 10.21.25.26
*#VRM Site Name - vSphereReplicationAsgard
*#vCenter Server Address - Yggdrasil.mhs.24pin.tech
*#vCenter Server Port - 80
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Migrating ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2022-10-13T20:34:46Z

Kwalters: /* Updating */

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi host to be able to install vCenter.
*Navigate to the location of the installer at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* Open up the installer and choose the install option. From here, simply follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*Select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the ITX password and continue.
*When starting the update, it may take anywhere from 30 minutes to several hours. Downtime is not required for the ESXi hosts that vCenter is managing, or for virtual machines that are running on the hosts. Only vCenter will be down and should start back up on it's own after the update.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the configuration for the machine using the following:
*# Password - (Your Choice)
*# NTP Server - 10.21.25.3
*# Hostname - vSphereReplicationAsgard
*# Default Gateway - 10.21.25.1
*# Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
*# Domain Name Servers - 10.21.25.3
*# Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
*# Management Network Netmask - 255.255.255.0

*Once you confirm the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface confirm that everything is set to the following
*VR>Configuration:
*#Hostname - vSphereReplicationAsgard.mhs.24pin.tech
*#Preferred DNS Server - 10.21.25.3
*#Alternate DNS Server - 10.21.25.4
*#Domain search path - Yggdrasil.mhs.24pin.tech
*#IPv4 Default Gateway - 10.21.25.1
*#IPv4 Address - 10.21.25.26
*#Netmask - 255.255.255.0
*Network>Address:
*#LookupService Address - yggdrasil.mhs.24pin.tech
*#VRM Host - 10.21.25.26
*#VRM Site Name - vSphereReplicationAsgard
*#vCenter Server Address - Yggdrasil.mhs.24pin.tech
*#vCenter Server Port - 80
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Migrating ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2022-10-13T20:28:39Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vCenter is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs.

=== Installing ===

* Before starting, you will need to have atleast one ESXi machine running to be able to install vCenter.
*The location of the installer can be found at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* When you first open up the installer you're given four options: install, upgrade, migrate, and restore. From here you just follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*When you go to update it will do two things, it will ask you to make a backup, and it will check the database health. For the backups you can select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the ITX password and continue. Now if you run into a issue with the database health you will have to refer to the article found in helpful links.
*When it gives you the option to start the update it might take a while, this is fine since the vCenter should start back up and resume on it's own.
*When updating, downtime is not required for the ESXi hosts that vCenter Server is managing, or for virtual machines that are running on the hosts.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the configuration for the machine using the following:
*# Password - (Your Choice)
*# NTP Server - 10.21.25.3
*# Hostname - vSphereReplicationAsgard
*# Default Gateway - 10.21.25.1
*# Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
*# Domain Name Servers - 10.21.25.3
*# Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
*# Management Network Netmask - 255.255.255.0

*Once you confirm the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface confirm that everything is set to the following
*VR>Configuration:
*#Hostname - vSphereReplicationAsgard.mhs.24pin.tech
*#Preferred DNS Server - 10.21.25.3
*#Alternate DNS Server - 10.21.25.4
*#Domain search path - Yggdrasil.mhs.24pin.tech
*#IPv4 Default Gateway - 10.21.25.1
*#IPv4 Address - 10.21.25.26
*#Netmask - 255.255.255.0
*Network>Address:
*#LookupService Address - yggdrasil.mhs.24pin.tech
*#VRM Host - 10.21.25.26
*#VRM Site Name - vSphereReplicationAsgard
*#vCenter Server Address - Yggdrasil.mhs.24pin.tech
*#vCenter Server Port - 80
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Migrating ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2022-10-13T20:27:33Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs. vSphere is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password.

=== Installing ===

* Before starting, you will need to have atleast one ESXi machine running to be able to install vCenter.
*The location of the installer can be found at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* When you first open up the installer you're given four options: install, upgrade, migrate, and restore. From here you just follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*When you go to update it will do two things, it will ask you to make a backup, and it will check the database health. For the backups you can select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the ITX password and continue. Now if you run into a issue with the database health you will have to refer to the article found in helpful links.
*When it gives you the option to start the update it might take a while, this is fine since the vCenter should start back up and resume on it's own.
*When updating, downtime is not required for the ESXi hosts that vCenter Server is managing, or for virtual machines that are running on the hosts.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the configuration for the machine using the following:
*# Password - (Your Choice)
*# NTP Server - 10.21.25.3
*# Hostname - vSphereReplicationAsgard
*# Default Gateway - 10.21.25.1
*# Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
*# Domain Name Servers - 10.21.25.3
*# Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
*# Management Network Netmask - 255.255.255.0

*Once you confirm the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface confirm that everything is set to the following
*VR>Configuration:
*#Hostname - vSphereReplicationAsgard.mhs.24pin.tech
*#Preferred DNS Server - 10.21.25.3
*#Alternate DNS Server - 10.21.25.4
*#Domain search path - Yggdrasil.mhs.24pin.tech
*#IPv4 Default Gateway - 10.21.25.1
*#IPv4 Address - 10.21.25.26
*#Netmask - 255.255.255.0
*Network>Address:
*#LookupService Address - yggdrasil.mhs.24pin.tech
*#VRM Host - 10.21.25.26
*#VRM Site Name - vSphereReplicationAsgard
*#vCenter Server Address - Yggdrasil.mhs.24pin.tech
*#vCenter Server Port - 80
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Migrating ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==

=== Potential Issues/Fixes ===

* Cant change root password:
#To change the password of the root user, access Asgard and open Yggdrasil in the console.
#From here, enter the root user and password to login.
#Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
*Changing root password (no password) - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html

* Checking the OVF files of the machine and if they are working - https://kb.vmware.com/s/article/2106709
*Lost Password - https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html
*Changing the IP interface if you can't access it - https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line
*404 Error - https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html
*VMware documentation on the setup - https://kb.vmware.com/s/article/2054994

VSphere

2022-10-13T20:23:56Z

Kwalters: /* Installing */

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs. vSphere is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password.

=== Installing ===

* Before starting, you will need to have atleast one ESXi machine running to be able to install vCenter.
*The location of the installer can be found at \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* When you first open up the installer you're given four options: install, upgrade, migrate, and restore. From here you just follow the steps in the installer to finish the installation.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*When you go to update it will do two things, it will ask you to make a backup, and it will check the database health. For the backups you can select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the ITX password and continue. Now if you run into a issue with the database health you will have to refer to the article found in helpful links.
*When it gives you the option to start the update it might take a while, this is fine since the vCenter should start back up and resume on it's own.
*When updating, downtime is not required for the ESXi hosts that vCenter Server is managing, or for virtual machines that are running on the hosts.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the configuration for the machine using the following:
*# Password - (Your Choice)
*# NTP Server - 10.21.25.3
*# Hostname - vSphereReplicationAsgard
*# Default Gateway - 10.21.25.1
*# Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
*# Domain Name Servers - 10.21.25.3
*# Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
*# Management Network Netmask - 255.255.255.0

*Once you confirm the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface confirm that everything is set to the following
*VR>Configuration:
*#Hostname - vSphereReplicationAsgard.mhs.24pin.tech
*#Preferred DNS Server - 10.21.25.3
*#Alternate DNS Server - 10.21.25.4
*#Domain search path - Yggdrasil.mhs.24pin.tech
*#IPv4 Default Gateway - 10.21.25.1
*#IPv4 Address - 10.21.25.26
*#Netmask - 255.255.255.0
*Network>Address:
*#LookupService Address - yggdrasil.mhs.24pin.tech
*#VRM Host - 10.21.25.26
*#VRM Site Name - vSphereReplicationAsgard
*#vCenter Server Address - Yggdrasil.mhs.24pin.tech
*#vCenter Server Port - 80
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Migrating ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==
Changing root password:
*To change the password of the root user, access Asgard and open Yggdrasil in the console.
*From here, enter the root user and password to login.
*Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
Other possible fixes:
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html Changing root password (no password)

*https://docs.vmware.com/en/vSphere-Replication/8.5/com.vmware.vsphere.replication-admin.doc/GUID-C987AD18-7C2D-4FA6-B6E4-6B0DDA915A7A.html (Entire VMware wiki for vSphere Replication)

* https://kb.vmware.com/s/article/2106709 (Checking the OVF files of the machine and if they are working)
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html (Lost password)
*https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line (Changing the IP interface if you can't access it)
*https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html (404 error)
*https://kb.vmware.com/s/article/2054994 #VMware documentation on the setup (ew)

VSphere

2022-10-12T03:33:01Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs. vSphere is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password.

=== Installing ===

* The location of the installer can be found \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* When you first open up the installer you're given four options: install, upgrade, migrate, and restore.
* From here you just follow the steps to installation. You will need to have a ESXi machine running to be able to install vCenter.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*I would choose the latest update available or if you are looking for a specific update you can mess with the update selection settings.
*When you go to update it will do two things, it will ask you to make a backup, and it will check the database health. For the backups you can select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the ITX password and continue. Now if you run into a issue with the database health you will have to refer to the article found in helpful links.
*When it gives you the option to start the update it might take a while, this is fine since the vCenter should start back up and resume on it's own.
*When updating, downtime is not required for the ESXi hosts that vCenter Server is managing, or for virtual machines that are running on the hosts.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
*To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
*It will ask you to choose local files for setup. For the setup, select the following files vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, and vSphere_Replication-system.vmdk from \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339

*Name the VM vSphereReplication and for the folder press the drop down and choose Discovered Virtual Machines.
*Agree to the license agreements and choose to deploy with 2 vCPUs.
* Next, chose the local machine datastore for both of the appliances we have in our network.
*For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
*Choose the configuration for the machine using the following:
*# Password - (Your Choice)
*# NTP Server - 10.21.25.3
*# Hostname - vSphereReplicationAsgard
*# Default Gateway - 10.21.25.1
*# Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
*# Domain Name Servers - 10.21.25.3
*# Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
*# Management Network Netmask - 255.255.255.0

*Once you confirm the machine will start deploying the OVF and you can see the progress below.
*When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5)
*Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface confirm that everything is set to the following
*VR>Configuration:
*#Hostname - vSphereReplicationAsgard.mhs.24pin.tech
*#Preferred DNS Server - 10.21.25.3
*#Alternate DNS Server - 10.21.25.4
*#Domain search path - Yggdrasil.mhs.24pin.tech
*#IPv4 Default Gateway - 10.21.25.1
*#IPv4 Address - 10.21.25.26
*#Netmask - 255.255.255.0
*Network>Address:
*#LookupService Address - yggdrasil.mhs.24pin.tech
*#VRM Host - 10.21.25.26
*#VRM Site Name - vSphereReplicationAsgard
*#vCenter Server Address - Yggdrasil.mhs.24pin.tech
*#vCenter Server Port - 80
*Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service.
*If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Migrating ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==
Changing root password:
*To change the password of the root user, access Asgard and open Yggdrasil in the console.
*From here, enter the root user and password to login.
*Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
Other possible fixes:
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html Changing root password (no password)

*https://docs.vmware.com/en/vSphere-Replication/8.5/com.vmware.vsphere.replication-admin.doc/GUID-C987AD18-7C2D-4FA6-B6E4-6B0DDA915A7A.html (Entire VMware wiki for vSphere Replication)

* https://kb.vmware.com/s/article/2106709 (Checking the OVF files of the machine and if they are working)
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html (Lost password)
*https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line (Changing the IP interface if you can't access it)
*https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html (404 error)
*https://kb.vmware.com/s/article/2054994 #VMware documentation on the setup (ew)

VSphere

2022-10-12T03:13:17Z

Kwalters: /* Moving Machines */

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs. vSphere is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password.

=== Installing ===

* The location of the installer can be found \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* When you first open up the installer you're given four options: install, upgrade, migrate, and restore.
* From here you just follow the steps to installation. You will need to have a ESXi machine running to be able to install vCenter.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*I would choose the latest update available or if you are looking for a specific update you can mess with the update selection settings.
*When you go to update it will do two things, it will ask you to make a backup, and it will check the database health. For the backups you can select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the ITX password and continue. Now if you run into a issue with the database health you will have to refer to the article found in helpful links.
*When it gives you the option to start the update it might take a while, this is fine since the vCenter should start back up and resume on it's own.
*When updating, downtime is not required for the ESXi hosts that vCenter Server is managing, or for virtual machines that are running on the hosts.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
(The process can also be followed at https://youtu.be/Y5idS2Z4ugs though our setup is slightly different because we only have one vCenter.) The entire installation process should be done via the vCenter console ([http://10.21.25.5/ 10.21.25.5]) and you will deploy the machine using [https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-AE61948B-C2EE-436E-BAFB-3C7209088552.html OVF files]. We have the replication ISO saved on \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339. The process can be followed here:
#To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
#It will ask you to choose local files for setup. You want to choose the following files (vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, vSphere_Replication-system.vmdk)
#The next couple of steps are self explanatory. It will ask for a name and folder. I would use the naming scheme vSphereReplication (the name of the machine the appliance is on.) As for the folder press the drop down and choose Discovered Virtual Machines.
#Compute resource is the machine that will be hosting the appliance. This is where the appliance will get it's resource pool from.
#Agree to the license agreements and press next. You will be asked if you want to deploy with 2vCPUs or 4vCPUs. I would choose 2vCPUs as 4 is overkill for our small network.
# Next it asks where you want to store the files for the appliance. I chose the local machine datastore for both of the appliances we have in our network, but you can also choose remote machines for more redundancy.
#For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
#This next step you will be actually choosing the configuration for the machine. The configuration I used was:
##Password - (Your Choice)
##NTP Server - 10.21.25.3
## Hostname - vSphereReplicationValhalla
##Default Gateway - 10.21.25.1
##Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
## Domain Name Servers - 10.21.25.3
##Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
##Management Network Netmask - 255.255.255.0
#The next two pages are just agreements and making sure these are the right settings.
#Once you confirm the machine will start deploying the OVF and you can see the progress below.
#'''When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5). I don't know why but if you turn on the machine for the first time on the ESXi machine the OVF doesn't get deployed right.'''
#Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface there will be a little more that you need to setup. You'll need to edit both VR>Configuration and Network>Address before you are able to start running the service. Our configuration can be found in the screenshots below.
#I had to change some things in the Configuration tab and the Address tab. The main things for those were changing the VRM Site Name to the name of the appliance, the Lookup Service Address to the domain name for the vCenter, and the DNS servers for the networking. If you don't do these correctly the service may not start and you may get a lookup service error.
#Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service. You have successfully deployed vSphere Replication Appliance.
#If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Migrating ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==
Changing root password:
*To change the password of the root user, access Asgard and open Yggdrasil in the console.
*From here, enter the root user and password to login.
*Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
Other possible fixes:
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html Changing root password (no password)

*https://docs.vmware.com/en/vSphere-Replication/8.5/com.vmware.vsphere.replication-admin.doc/GUID-C987AD18-7C2D-4FA6-B6E4-6B0DDA915A7A.html (Entire VMware wiki for vSphere Replication)

* https://kb.vmware.com/s/article/2106709 (Checking the OVF files of the machine and if they are working)
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html (Lost password)
*https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line (Changing the IP interface if you can't access it)
*https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html (404 error)
*https://kb.vmware.com/s/article/2054994 #VMware documentation on the setup (ew)

VSphere

2022-10-12T03:12:54Z

Kwalters: /* Updating: */

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs. vSphere is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password.

=== Installing ===

* The location of the installer can be found \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* When you first open up the installer you're given four options: install, upgrade, migrate, and restore.
* From here you just follow the steps to installation. You will need to have a ESXi machine running to be able to install vCenter.

=== Updating ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*I would choose the latest update available or if you are looking for a specific update you can mess with the update selection settings.
*When you go to update it will do two things, it will ask you to make a backup, and it will check the database health. For the backups you can select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the ITX password and continue. Now if you run into a issue with the database health you will have to refer to the article found in helpful links.
*When it gives you the option to start the update it might take a while, this is fine since the vCenter should start back up and resume on it's own.
*When updating, downtime is not required for the ESXi hosts that vCenter Server is managing, or for virtual machines that are running on the hosts.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
(The process can also be followed at https://youtu.be/Y5idS2Z4ugs though our setup is slightly different because we only have one vCenter.) The entire installation process should be done via the vCenter console ([http://10.21.25.5/ 10.21.25.5]) and you will deploy the machine using [https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-AE61948B-C2EE-436E-BAFB-3C7209088552.html OVF files]. We have the replication ISO saved on \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339. The process can be followed here:
#To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
#It will ask you to choose local files for setup. You want to choose the following files (vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, vSphere_Replication-system.vmdk)
#The next couple of steps are self explanatory. It will ask for a name and folder. I would use the naming scheme vSphereReplication (the name of the machine the appliance is on.) As for the folder press the drop down and choose Discovered Virtual Machines.
#Compute resource is the machine that will be hosting the appliance. This is where the appliance will get it's resource pool from.
#Agree to the license agreements and press next. You will be asked if you want to deploy with 2vCPUs or 4vCPUs. I would choose 2vCPUs as 4 is overkill for our small network.
# Next it asks where you want to store the files for the appliance. I chose the local machine datastore for both of the appliances we have in our network, but you can also choose remote machines for more redundancy.
#For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
#This next step you will be actually choosing the configuration for the machine. The configuration I used was:
##Password - (Your Choice)
##NTP Server - 10.21.25.3
## Hostname - vSphereReplicationValhalla
##Default Gateway - 10.21.25.1
##Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
## Domain Name Servers - 10.21.25.3
##Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
##Management Network Netmask - 255.255.255.0
#The next two pages are just agreements and making sure these are the right settings.
#Once you confirm the machine will start deploying the OVF and you can see the progress below.
#'''When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5). I don't know why but if you turn on the machine for the first time on the ESXi machine the OVF doesn't get deployed right.'''
#Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface there will be a little more that you need to setup. You'll need to edit both VR>Configuration and Network>Address before you are able to start running the service. Our configuration can be found in the screenshots below.
#I had to change some things in the Configuration tab and the Address tab. The main things for those were changing the VRM Site Name to the name of the appliance, the Lookup Service Address to the domain name for the vCenter, and the DNS servers for the networking. If you don't do these correctly the service may not start and you may get a lookup service error.
#Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service. You have successfully deployed vSphere Replication Appliance.
#If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Moving Machines ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==
Changing root password:
*To change the password of the root user, access Asgard and open Yggdrasil in the console.
*From here, enter the root user and password to login.
*Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
Other possible fixes:
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html Changing root password (no password)

*https://docs.vmware.com/en/vSphere-Replication/8.5/com.vmware.vsphere.replication-admin.doc/GUID-C987AD18-7C2D-4FA6-B6E4-6B0DDA915A7A.html (Entire VMware wiki for vSphere Replication)

* https://kb.vmware.com/s/article/2106709 (Checking the OVF files of the machine and if they are working)
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html (Lost password)
*https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line (Changing the IP interface if you can't access it)
*https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html (404 error)
*https://kb.vmware.com/s/article/2054994 #VMware documentation on the setup (ew)

VSphere

2022-10-12T03:12:32Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our [[ESXi]] hosts together and manage them all from a single place. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs. vSphere is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password.

=== Installing: ===

* The location of the installer can be found \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* When you first open up the installer you're given four options: install, upgrade, migrate, and restore.
* From here you just follow the steps to installation. You will need to have a ESXi machine running to be able to install vCenter.

=== Updating: ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*I would choose the latest update available or if you are looking for a specific update you can mess with the update selection settings.
*When you go to update it will do two things, it will ask you to make a backup, and it will check the database health. For the backups you can select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the ITX password and continue. Now if you run into a issue with the database health you will have to refer to the article found in helpful links.
*When it gives you the option to start the update it might take a while, this is fine since the vCenter should start back up and resume on it's own.
*When updating, downtime is not required for the ESXi hosts that vCenter Server is managing, or for virtual machines that are running on the hosts.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== Installation ===
(The process can also be followed at https://youtu.be/Y5idS2Z4ugs though our setup is slightly different because we only have one vCenter.) The entire installation process should be done via the vCenter console ([http://10.21.25.5/ 10.21.25.5]) and you will deploy the machine using [https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-AE61948B-C2EE-436E-BAFB-3C7209088552.html OVF files]. We have the replication ISO saved on \\midgard\Cisco Curriculum\vSphere Downloads\VMWare-vSphere_Replication-8.3.1-17210339. The process can be followed here:
#To deploy a vSphere Replication machine you want to make sure you are in the hosts section of vCenter and you want to right click the machine you are deploying the appliance on and choose "Deploy OVF Template."
#It will ask you to choose local files for setup. You want to choose the following files (vSphere_Replication_OVF10.ovf, vSphere_Replication-support.vmdk, vSphere_Replication-system.vmdk)
#The next couple of steps are self explanatory. It will ask for a name and folder. I would use the naming scheme vSphereReplication (the name of the machine the appliance is on.) As for the folder press the drop down and choose Discovered Virtual Machines.
#Compute resource is the machine that will be hosting the appliance. This is where the appliance will get it's resource pool from.
#Agree to the license agreements and press next. You will be asked if you want to deploy with 2vCPUs or 4vCPUs. I would choose 2vCPUs as 4 is overkill for our small network.
# Next it asks where you want to store the files for the appliance. I chose the local machine datastore for both of the appliances we have in our network, but you can also choose remote machines for more redundancy.
#For the networking machine choose the management network for the machine you are deploying on and keep it as static-manual IPv4.
#This next step you will be actually choosing the configuration for the machine. The configuration I used was:
##Password - (Your Choice)
##NTP Server - 10.21.25.3
## Hostname - vSphereReplicationValhalla
##Default Gateway - 10.21.25.1
##Domain Name & Domain Search Path - Yggdrasil.mhs.24pin.tech (this will typically be the central vCenter along with your domain name)
## Domain Name Servers - 10.21.25.3
##Management IP Address - 10.21.25.25 (The IP address you will use to configure the appliance)
##Management Network Netmask - 255.255.255.0
#The next two pages are just agreements and making sure these are the right settings.
#Once you confirm the machine will start deploying the OVF and you can see the progress below.
#'''When the machine is done make sure to start the machine up for the first time on the vCenter (10.21.25.5). I don't know why but if you turn on the machine for the first time on the ESXi machine the OVF doesn't get deployed right.'''
#Once the machine boots up and says you can manage it from the web interface go ahead and do so. The login should be root and the password you set. Now that you are in the web interface there will be a little more that you need to setup. You'll need to edit both VR>Configuration and Network>Address before you are able to start running the service. Our configuration can be found in the screenshots below.
#I had to change some things in the Configuration tab and the Address tab. The main things for those were changing the VRM Site Name to the name of the appliance, the Lookup Service Address to the domain name for the vCenter, and the DNS servers for the networking. If you don't do these correctly the service may not start and you may get a lookup service error.
#Once you have inputted all of your information you will be able to head back over to the VR>Configuration tab and press the Save and Restart Service. You have successfully deployed vSphere Replication Appliance.
#If you have rebuilt the replications VM make sure to delete any old replications from the datastore so it doesn't waste tons of space.
=== '''Replicating:''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring:''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range.

=== Moving Machines: ===
* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* Choose to change both computer resource and storage
* Choose the machine you are migrating the machine to by dropping down the cluster. When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached.
* Choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal.
* Choose the networking group the machine we part of, which should usually be the default port group depending on the machine.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation: ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting: ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==
Changing root password:
*To change the password of the root user, access Asgard and open Yggdrasil in the console.
*From here, enter the root user and password to login.
*Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
Other possible fixes:
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html Changing root password (no password)

*https://docs.vmware.com/en/vSphere-Replication/8.5/com.vmware.vsphere.replication-admin.doc/GUID-C987AD18-7C2D-4FA6-B6E4-6B0DDA915A7A.html (Entire VMware wiki for vSphere Replication)

* https://kb.vmware.com/s/article/2106709 (Checking the OVF files of the machine and if they are working)
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html (Lost password)
*https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line (Changing the IP interface if you can't access it)
*https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html (404 error)
*https://kb.vmware.com/s/article/2054994 #VMware documentation on the setup (ew)

VSphere

2022-10-12T03:07:42Z

Kwalters:

VSphere

2022-10-12T03:06:23Z

Kwalters: /* Moving Machines: */

VSphere

2022-10-12T03:05:20Z

Kwalters: /* vMotion */

VSphere

2022-10-12T03:00:06Z

Kwalters: /* VM Snapshots */

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our ESXi hosts together and manage them all from a single place. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs. vSphere is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password.

=== Installing: ===

* The location of the installer can be found \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* When you first open up the installer you're given four options: install, upgrade, migrate, and restore.
* From here you just follow the steps to installation. You will need to have a ESXi machine running to be able to install vCenter.

=== Updating: ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*I would choose the latest update available or if you are looking for a specific update you can mess with the update selection settings.
*When you go to update it will do two things, it will ask you to make a backup, and it will check the database health. For the backups you can select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the ITX password and continue. Now if you run into a issue with the database health you will have to refer to the article found in helpful links.
*When it gives you the option to start the update it might take a while, this is fine since the vCenter should start back up and resume on it's own.
*When updating, downtime is not required for the ESXi hosts that vCenter Server is managing, or for virtual machines that are running on the hosts.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== '''Replicating:''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring:''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range and a little bit of understanding about networking. To use the feature of vMotion you will need to have a vSphere/vCenter in your environment. This is a central manage point in the VMware environment and more can be read about it on the dedicated wiki page about it. Actually moving machines over is pretty simple and can be done by following this process:

* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* For my purposes I always use the "Change both computer resource and storage" option. In other environments this may be different but because ours is a little simple we use this option
* Next you will need to choose the machine you are migrating the machine to, to do this you drop down the cluster and choose the machine
** When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached. An example of this is usually Friia has some sort of hard drive attached, just go into the VM settings and uncheck the box next to the device.
* If everything went right from the option above the next step should be to choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal. I keep the other settings the same.
* Next you choose the networking group the machine we part of. This should just be the default port group depending on the machine. On Valhalla and Asgard I kept the port group stuff the default so it doesn't get too unnecessarily complicated.
* Now you just need to choose if you want to do the migration with high priority or normal, it doesn't really matter in our small environment, I usually just do the high priority.

==Snapshots==
Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation: ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting: ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==
Changing root password:
*To change the password of the root user, access Asgard and open Yggdrasil in the console.
*From here, enter the root user and password to login.
*Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
Other possible fixes:
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html Changing root password (no password)

*https://docs.vmware.com/en/vSphere-Replication/8.5/com.vmware.vsphere.replication-admin.doc/GUID-C987AD18-7C2D-4FA6-B6E4-6B0DDA915A7A.html (Entire VMware wiki for vSphere Replication)

* https://kb.vmware.com/s/article/2106709 (Checking the OVF files of the machine and if they are working)
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html (Lost password)
*https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line (Changing the IP interface if you can't access it)
*https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html (404 error)
*https://kb.vmware.com/s/article/2054994 #VMware documentation on the setup (ew)

VSphere

2022-10-12T02:59:41Z

Kwalters:

== vSphere/vCenter ==
vSphere is VMWare's virtualization platform and a central planning/management area to work on VMWare products. In vSphere, we use vCenter to connect all of our ESXi hosts together and manage them all from a single place. vSphere also adds other services such as vSphere Replication to the environment which allows us to take daily replications of our VMs. vSphere is located on a virtual machine on 10.21.25.2 called Yggdrasil. It can be accessed at <nowiki>https://10.21.25.5</nowiki> with the login administator@vsphere.local and the highest level pintech password.

=== Installing: ===

* The location of the installer can be found \\10.21.25.13/Cisco Curriculum/vSphere Downloads/VMware-VCSA-all-7.0.3-18778458/vcsa-ui-installer/win32/installer
* When you first open up the installer you're given four options: install, upgrade, migrate, and restore.
* From here you just follow the steps to installation. You will need to have a ESXi machine running to be able to install vCenter.

=== Updating: ===
*To start the update process you want to go and head over to the vCenter management web interface at https://yggdrasil.mhs.24pin.tech:5480/#/login.
*Go to the update section of the page and wait for the available updates to load.
*I would choose the latest update available or if you are looking for a specific update you can mess with the update selection settings.
*When you go to update it will do two things, it will ask you to make a backup, and it will check the database health. For the backups you can select backup now and check the box that says use the scheduled update settings. From there you will just need to put in the ITX password and continue. Now if you run into a issue with the database health you will have to refer to the article found in helpful links.
*When it gives you the option to start the update it might take a while, this is fine since the vCenter should start back up and resume on it's own.
*When updating, downtime is not required for the ESXi hosts that vCenter Server is managing, or for virtual machines that are running on the hosts.
==vSphere Replication==
vSphere Replication is a appliance offered by VMWare for their vCenter servers. We have it setup so that our vSphere replication appliance and vCenter are both on Asgard. You can choose which VMs you want to replicate and how often they sync/replicate so you can restore to a previous version if something ever goes wrong. Replications can be accessed at 10.21.25.26 using administrator@vsphere.local and the highest level password. Once you are in, you can view the replications by clicking view details and then the pressing the replication tab.

=== '''Replicating:''' ===
*For the target site choose manually select and then select vSphereReplicationAsgard
*Choose the machine you want to replicate
*For the target datastore choose the opposite of what the machine is currently on
*Change the replication time to every 24 hours
*Press finish to start the initial sync of the machine (you can check the progress of the replication by using the drop down)

=== '''Restoring:''' ===
*Right click the machine you want to restore and then press the recover button
*When choosing you recovery options you want to use the latest available data if it is a restoration of a broken machine, or in very small cases sync most available data for other reasons. Also make sure the machine doesn’t turn on at start, this is for later.
*For the machine you want to choose the opposite of what the current machine is on (example: the web server is on Valhalla so we would choose Asgard) and then press finish.
*Mark the checkbox next to the VM Network option in the VM settings if it is not connecting to the network.
*When finished, be sure to always change the name of the broken server and the working one to easily differentiate them.
*Once you restore a machine you have to make sure you delete the replication and then create it again for the new working machine.

== vMotion ==
This is a core feature to the VMware environment and allows machine to migrate over between ESXi boxes with zero down time. In order to configure vMotion you need to have two available IP addresses in your reservation range and a little bit of understanding about networking. To use the feature of vMotion you will need to have a vSphere/vCenter in your environment. This is a central manage point in the VMware environment and more can be read about it on the dedicated wiki page about it. Actually moving machines over is pretty simple and can be done by following this process:

* Login into your vCenter/vSphere appliance and find the machine you want to move over with zero downtime
* Right click the machine and press on the Migrate option
* For my purposes I always use the "Change both computer resource and storage" option. In other environments this may be different but because ours is a little simple we use this option
* Next you will need to choose the machine you are migrating the machine to, to do this you drop down the cluster and choose the machine
** When doing this you may get an error or two, usually this is due to the fact some sort of device is attached to the VM and you just need to go and configure the VM to make sure no external devices are attached. An example of this is usually Friia has some sort of hard drive attached, just go into the VM settings and uncheck the box next to the device.
* If everything went right from the option above the next step should be to choose the datastore. Here you can verify that you chose the right machine since you should only have one option, either ValhallaLocal or AsgardLocal. I keep the other settings the same.
* Next you choose the networking group the machine we part of. This should just be the default port group depending on the machine. On Valhalla and Asgard I kept the port group stuff the default so it doesn't get too unnecessarily complicated.
* Now you just need to choose if you want to do the migration with high priority or normal, it doesn't really matter in our small environment, I usually just do the high priority.

==VM Snapshots==
VM Snapshots are short term restore options that can be created before you apply major updates or changes to a virtual machine. It allows you to create multiple restore points of your virtual machine as you go through the update process. Snapshots must be deleted to update the storage of any VM.

=== Creation: ===

* Select the VM you want to create a snapshot of and navigate to the snapshot tab.

*Press take snapshot to create a snapshot (write why the snapshot is being taken in the description)
*Uncheck VM memory when taking snapshots of Yggdrasil or vSphereReplication

=== Reverting: ===
*Select the VM you want to create a snapshot of and navigate to the snapshot tab.
*Click on the snapshot you want to revert to and then press finish to restore the VM to the snapshot.
*Once you have fixed the issue, make sure to delete that snapshot and then create a new snapshot for the latest version.
==Troubleshooting==
Changing root password:
*To change the password of the root user, access Asgard and open Yggdrasil in the console.
*From here, enter the root user and password to login.
*Once you have logged in, type ''shell'' and then type ''passwd'' to create a new password.
Other possible fixes:
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html Changing root password (no password)

*https://docs.vmware.com/en/vSphere-Replication/8.5/com.vmware.vsphere.replication-admin.doc/GUID-C987AD18-7C2D-4FA6-B6E4-6B0DDA915A7A.html (Entire VMware wiki for vSphere Replication)

* https://kb.vmware.com/s/article/2106709 (Checking the OVF files of the machine and if they are working)
*https://vmware.github.io/photon/assets/files/html/3.0/photon_troubleshoot/resetting-a-lost-root-password.html (Lost password)
*https://serverfault.com/questions/459948/how-to-change-vcenter-server-appliance-ip-from-command-line (Changing the IP interface if you can't access it)
*https://williamlam.com/2020/11/why-am-i-seeing-http-communication-status-404-error-when-configuring-vsphere-with-tanzu-how-to-fix.html (404 error)
*https://kb.vmware.com/s/article/2054994 #VMware documentation on the setup (ew)

VSphere

2022-10-12T02:57:46Z

Kwalters: /* ESXi */