When trying to run reports we receive the following error:
Recently did a rack migration for which we had to shutdown SQL cluster and vCenter server including all Virtual machines.
After powering I was unable to login with my domain account and got the following error:
“Failed to connect to VMware Lookup Service. SSL certificate verification failed”
- Login to vCenter server (SSH or RDP depending on vCenter server platform) and verified that the vmware-sso service is running.
- Could not login with local firstname.lastname@example.org so logged into VA configuration https://:5480. Verified all services was running.
- Verified SSO server and Active directory domain controllers time is not off by more than 5 minutes.
- Found KB article on this error.
Found KB that provides information on this issue which seems to get triggered when you had change the IP or hostname of the vCenter server after its initial creation.
To fix the issue login to VA configuration: https://:5480.
Select admin tab
Check the “yes” radio button for “Certificate regeneration enabled:”
Restart vCenter server
So recently i was asked to assist with setting up a new SQL 2012 AlwaysOn Cluster for POC.
During the configuration of the VM’s we had to setup a quorom disk which is shared between both servers for MSCS.
The shared disk I configured and select virtual device node on newly created SCSI controller, LSI Logic SAS with SCSI bus sharing set to Physical.
On the 2nd VM i created the same SCSI controller as above and instead of creating new disk the existing disk was select.
With Primary powered on and trying to power on the 2nd SQL server i receive the following error:
“Could not open/create change tracking file”
The error eludes to problem with CBT on the Virtual server where i cannot access the cbt file due to the primary VM already running and locked the file.
I could not find much information in documentation regarding setting up clusters or shared vmdk disk and making use of CBT.
It does however seem that CBT has some restrictions:
- The virtual machine version earlier than 7
- The virtual machine has a Raw Device Mapping (RDM) in the physical compatibility mode.
- The virtual machine has a disk attached to a shared virtual SCSI bus. Use of CBT only possible when SCSI bus sharing is set to none.
- Edit settings of virtual machine
- Select options tab
- Click General under advanced -> configuration parameters
- Click Add row
- Add “ctkEnabled and set value “false” (this will set for all devices)
- Add “scsi0:0.ctkEnabled and set value “false” (this will set for specific devices)
- SSH to ESXi host
- browse the datastore where VM resides
- Open the .vmx file of the virtual machine using a text editor.
- Add this entry to the file:
Setting your host with NTP services using host profiles requires a few changes to be made in different settings on host profiles.
Edit the host profile
- Lets first set the NTP servers:
- General system settings -> Date and Time configuration
- Click Date and time configuration
- Time settings – “Configure a fixed NTP configuration”
- List of time servers – add server IP address or FQDN for NTP servers. Use comma to list multiple servers
- Now lets enable the NTP service:
- Security and services -> Services configuration -> Services configuration
- Select NTPD (make sure this is enabled)
- On service verify the dropdown box is set to “Establish a fixed service configuration”
- Policy that dictates how the service will be handled – type “on”
- Now lets set the firewall rule:
- Security and services -> Firewall configuration -> Firewall configuration -> Ruleset Configuration
- Select ntpClient (make sure this is enabled)
- Verify dropdown “Specify the configuration of a fixed ruleset.
- Check the box for enabled on “Flag indication where ruleset should be enabled”
- Check the box for enabled on “Flag indication where ruleset should allow all ip addresses” (this is self explanatory)
Setup host profiles and when applied on other hosts i get receive the error message:
Seems that ESXi treats SAS disk as shared disks instead of local disks which causes these errors when you create your host profile from an existing ESXi host.
The only workaround I found is to disable the following settings in the host profile –
- Storage configuration – > Pluggable Storage Architecture (PSA) configuration
- disable “PSA device settings”
- disable “PSA device configuration”
- Storage configuration -> Native Multi-Pathing NMP
- disable “PSP and SATP configuration for NMP devices
- Equipment tab -> equipment – > policies tab
- Equipment tab -> select FI-A/B -> expand -> fixed modules
- Configure the appropriate unconfigured ports as “Server” (connections between IOM and Fabric Interconnect) and “Uplink” (connection to network)
- Equipment tab
- All the way bottom, select FI A
- Right hand side select Configure unified ports
- Run slider to end of fiber storage ports you need
- This will reboot FIA, after reboot re-login.
- Select FI B
- Perform same steps
- Setup ports as uplink ports
- LAN TAB
- Fabric – Port Channels
- Setup port channel ..set same PORT ID on both Fis
- SAN TAB ( will not be creating port channel due to connection to Brocade)
- San Cloud -> Fabric A -> Under general tab select “create Port Channel”
- SAN > SAN Cloud > Fabric A > VSANs (both Fabric A & B)
- Create VSAN
- Select the specific Fabric A or B (not common)!
- Assign VSAN to FC uplinks
- Equipment tab -> Fabric interconnect A & B -> Fixed modules -> FC ports
- Select FC port
- Under general tab click drop down for VSAN.
- Select VSAN which is associated to FI.
- . An “*.A.bin” file and a “*.B.bin” file. The “*.B.bin” file contains all of the firmware for the B-Series blades. The “*.A.bin” file contains all the firmware for the Fabric Interconnects, I/O Modules and UCS Manage
- Equipment tab -> Eqiupment -> Firmware management
- Download firmware
- Update firmware (view progress under Firmware auto install -> general tab, or press Apply to view status in same window))
- Activate firmware in the following order: Choose “Ignore Compatibility Check” anywhere applicable.
- UCS manager
- I/O Modules
- Choose “skip validation” anywhere applicable. Make sure to uncheck “Set startup version only”, since this is an initial setup and we aren’t concerned with rebooting running hosts
- Activate subordinate FI and then primary FI
- Right click and root directory, select Create organization
- Specify name
- Lab tab -> pools -> root -> IP Pools -> IP Pool ext-mgmt
- Create block of IPv4 Addresses
- Specify IP range
- Servers tab -> Pools -> Sub-Organization -> -> Server pools
- Create server pool
- Servers tab -> Pools -> Sub-Organization -> -> UUID Suffix Pool
- Create UUID suffix pool
- Create Suffixes
- For each suborganization create 2 groups of MAC pools. 1 for FI-A and 1 for FI-B
- LAN TAB: -> Pools -> Root -> MAC Pools
- Create new pool for A
- Create block
- Create new pool for B
- SAN TAB:
- Pools -> root -> sub-organization -> WWNN Pools
- Create WWNN pool
- Add double the amount since each server will have two HBA’s
- For WWPN we will again create separate pools for FI-A and FI-B:
- LAN TAB -> Lan -> Lan Cloud -> VLANs
- Create new VLANs
- Provide name and ID
- LAB TAB -> LAN -> Policies -> root -> Sub-organization -> vNIC templates
- Create vNIC template (this is again done for each FI-A and FI-B
- SAN TAB -> Policies -> root -> sub-organizations -> vHBA templates
- Create vHBA Templates for both FI-A & FI-B
- Create service profile template
- LAB tab -> Policies -> root -> sub-organizations -> network control policies
- Create network control policy
- Enable CDP
- Servers tab -> Policies -> root -> sub-organizations -> Bios Policies
- Create bios policies
- Mostly setting cpu settings
- Servers tab -> Policies -> root -> sub-organizations -> Host Firmware Packages
- Create host firmware package
- Set simple and only blade package version.
- Servers tab -> Policies -> root -> sub-organizations -> Local disk config policies
- Servers tab -> Policies -> root -> sub-organizations -> maintenance policies
- Create Maintenance Policy
- Servers tab -> Policies -> root -> sub-organizations -> boot policies
- Create boot policy
- Expand local devices and add to boot order
- Start with Local CD, then remote virtual drive then SD card