configuration-of-a-nested-vsphere-6-0-esxi-host

Configuration of  a nested vSphere 6.0 ESXi Host

Configuring the ESXi

The ESXi is installed. Next steps are to configure the ESXi and add it to the vCenter.

When booting the host it will try to fetch an IP-address using DHCP. Since I don’t want to use (and wouldn’t recommend) DHCP for hypervisors I’ll reconfigure the host. It’s also possible to setup a network-redundancy within this configuration.

vSphere 6.0 ESXi Host

To enter the DCUI just access the console and hit F2.

The console will ask for the root password to grant you access.

After entering your password the configuration menu will show up. This menu contains all you need to initially set up several configurations (mostly network, but also keyboard configuration), test the network, do some troubleshooting, view the systems logs and reset the system.

vSphere ESXi 6.0 setup pw

First things first, so lets head to the network configuration using Configure Management Network.

Since there is only one network adapter and the vlan is already set only level “higher”, I only have to configure the IPv4 Configuration and DNS Configuration.

vSphere ESXi 6 Network

As you can see it already fetched some IP configuration from the DHCP. But that’s not what I want to use. So changing it to Set static IPv4 address and network configuration by selecting it with the arrow down and mark it and hit space for the configuration I will use my already reserved IPv4 Address 192.168.99.154 with Subnet Mask 255.255.255.0 and Default Gateway 192.168.99.1. Saving the settings using Enter.

ESXi 6.0 Network Setup

Next step is the DNS Configuration.

By default it’s already changed to Use the following DNS server addresses and hostname because of turning of DHCP in the IPv4 configuration.

Checking the existing Primary DNS Server and Alternate DNS Server which the ESXi host set automatically from the DHCP lease. And setting the Hostname to the correct Server name esxqa6-1 (underscore in Hostnames are not accepted). Saving using Enter again.

vSphere ESXi 6.0 dns

If you are having a domain in you infrastructure you might add it to the Custom DNS Suffixes. Doing so it is possible to use short, unqualified names.

When the network configuration is complete hit the Esc-Key to exit the Configure Management Network dialog.

The configuration will ask if you really want to Apply changes and restart management network? – answering Y for yes saves the changes and restarts the management network. Totally fine in this case as nothing is running on the hosts and it isn’t connected to a monitoring or management system.

Finally testing the network using the Test Management Network.

ESXi 6.0 Testing management network

By default it will try to ping the gateway, the primary DNS, the alternative DNS and it will try to resolve the hostname of itself.

All test passed except resolving the hostname (which is totally fine because it’s not added to the DNS by now).

At this point the configuration is complete. Now logging out using Esc and adding the host to the vCenter is next.

You can add the vSphere 6.0 ESXi Host now to the vCenter

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.