Skip to Content
  •  +49 (861) 88 00 32 00
COD powered by extocode GmbH
  • 0
  • Sign in
  • English (US) Français Deutsch Español Türkçe
  • Open the demo
  • Home
  • COD Overview
    Platform
    OverviewPlatform: tenants and brandFeaturesProblems & SolutionsArchitectureDocumentationIntegrationsPricing
    Operations & Network
    MonitoringNetworkNetwork Access Control (NAC)TACACS+Captive PortalFirewall
    Security & Resilience
    Governance, Risk & ComplianceBackupHypervisorOTPPasskeeprAutomation
    Solutions & More
    NIS2 & CompliancecodPassAI documentation (InfraScan add-on)Open the demoReferencesDownloadsFAQ
  • Pricing
  • News
    • Blog
    • Roadmap
  • FAQ
  • About us
    • About us
    • Careers
    • Partners
    • References
  • Academy
  • Contact
COD powered by extocode GmbH
  • 0
    • Home
    • COD Overview
    • Pricing
    • News
      • Blog
      • Roadmap
    • FAQ
    • About us
      • About us
      • Careers
      • Partners
      • References
    • Academy
    • Contact
  •  +49 (861) 88 00 32 00
  • English (US) Français Deutsch Español Türkçe
  • Sign in
  • Open the demo
  1. Home
  2. Documentation
  3. Modules
  4. Hypervisor

Hypervisor

This page describes how the Hypervisor module connects to vCenter and ESXi, what it changes there and where its limits are.

What the module does is described on the module page.

As of: November 2026, COD 3.8.6

Documentation contents
  • Overview
  • Getting started
  • Requirements
  • Names and addresses
  • Network devices
  • Time and DNS
  • Installation
  • Deployment shapes
  • Initial setup
  • Updates
  • Modules
  • Network and MikroTik
  • Automation
  • NAC
  • TACACS+
  • Firewall
  • Captive Portal
  • Monitoring
  • Backup
  • Hypervisor
  • OTP
  • Passkeepr
  • GRC
  • Inventory and CMDB import
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

Documentation

  • Overview
  • Getting started
  • Requirements
  • Names and addresses
  • Network devices
  • Time and DNS
  • Installation
  • Deployment shapes
  • Initial setup
  • Updates
  • Modules
  • Network and MikroTik
  • Automation
  • NAC
  • TACACS+
  • Firewall
  • Captive Portal
  • Monitoring
  • Backup
  • Hypervisor
  • OTP
  • Passkeepr
  • GRC
  • Inventory and CMDB import
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

Overview

PropertyValue
PurposeRead the host network. Create, change and delete standard vSwitches and port groups. Detect differing port group names per VLAN
Supported systemsVMware vCenter and ESXi. Not other hypervisors such as Hyper-V or KVM
InterfaceVMware API through the Python library pyVmomi, over HTTPS
Connection and directionThe cod-hypervisor service on the COD server opens the connection to vCenter or ESXi
ServiceAlways runs on the COD server, never on a module server
CredentialsHostname, domain, user and password per connection. COD stores the connections per location
Rights on the targetRead access for the inventory. For changes, rights on the host network. You receive the minimum rights as part of the project.
Link to other modulesNone. The module is not linked with Asset, Network or Firewall

Requirements

On the COD server

  • Package cod-hypervisor installed. It is part of cod-all.
  • The service runs on the same host as COD. COD only addresses it locally.
  • The COD server reaches vCenter or the ESXi hosts over HTTPS.

Customers and partners receive the list of connections and firewall rules as part of the project.

In vCenter or ESXi

  • A dedicated service account for COD, recommended. Changes made from COD then stay traceable in vSphere.
  • Read access to datacenters, clusters, hosts and networks for the inventory.
  • For changes, rights on the vSwitches and port groups of the hosts. You receive the minimum rights as part of the project.
  • Each ESXi host appears under only one of the connected vCenters.

In COD

  • Hypervisor module enabled for the tenant.
  • A role with the permission for the Hypervisor module.

Setup

The rollout wizard does not cover the Hypervisor module. You set up the service on the COD server.

  1. Check on the COD server that the service is running: systemctl status cod-hypervisor. Details under TACACS+ and Hypervisor by hand.
  2. The manager account enables the module: “Admin Area > Tenant > Modules”. Then sign out and in again.
  3. Choose the location in the top bar.
  4. In the Hypervisor module, create a connection under “Connections”: hostname, domain, user, password.
  5. Check the inventory. It shows datacenters, clusters, hosts, vSwitches and port groups.
  6. Change port groups first under “Port Groups” with a dry run. Write to the hosts only once the result is right.

For further vCenters, create a separate connection per vCenter.

Technical details

Connection

COD talks to vCenter and ESXi through the VMware API, using the Python library pyVmomi over HTTPS. You do not enter credentials with every call. COD stores each connection with hostname, domain, user and password per location. Whoever uses the module at a location works with that location's connections.

Inventory

LevelWhat COD shows
Datacenter, cluster, hostObject tree from vCenter, read only
vSwitchStandard vSwitches per host, with active, standby and unused NICs and security settings
Port groupName and VLAN ID
Physical NICspNICs per host

The hypervisor tree is one of the sources of the global search.

Functions

FunctionWhereDry run
Create a vSwitch, per host with chosen physical NICs as uplinksWizard under “Structure”no, writes immediately
Create a port groupWizard under “Structure”no, writes immediately
Create, change, delete port groups“Port Groups”yes, on by default
Detect differing port group namesInventorynot needed, read only

VLAN IDs

ValueMeaning
1 to 4095VLAN ID when creating a port group
0 in the inventoryUntagged
4095 in the inventoryTrunk across all VLANs

Several hosts

Operations accept a list of hosts. The result reports success or failure per host. After every change, check the hosts with errors one by one.

Differing names

COD reports when the same VLAN ID is carried under different port group names on identically named vSwitches across hosts. This is a common cause of failed VM migrations.

NIC teaming

COD shows the NIC assignment per vSwitch. When you create a vSwitch, you choose the physical NICs as uplinks. Load balancing and security policies are still set in vSphere.

Audit

Changes appear in the Admin Area audit, with type, data sent and returned, time and user. Dry runs and the wizard under “Structure” do not appear there.

Known limits

LimitWhat you can do
Standard vSwitches only, no distributed switchesKeep managing distributed switches in vSphere
No VM control, no lifecycle of VMs or hostsUse vSphere for this
No link to Asset, Network or FirewallAlso keep ESXi hosts as assets if you need them there
An ESXi host under two vCenters breaks the synchronisationConnect each ESXi host through one vCenter only
Dry run only under “Port Groups”Use the wizard under “Structure” with care, for example in a maintenance window
The wizard under “Structure” does not appear in the auditDocument these changes yourself
No merged view across several vCentersWork per connection
Load balancing and security policies not in CODSet them in vSphere
Service only on the COD serverPlan the path from the COD server to vCenter and ESXi
Minimum rights in vCenter not documentedYou receive the minimum rights as part of the project.

Further reading

  • Hypervisor module page
  • What your network needs for Hypervisor
  • Deployment shapes
  • Troubleshooting
  • Integrations
  • Questions about the modules
← Previous: BackupNext: OTP →
Folgen Sie uns
​
  • COD Overview
  • Features
  • Demo
  • Pricing
  • Integrations
  • NIS2
  • codPass
  • References

Help

  • FAQ
  • Documentation
  • Downloads
  • Contact

Kotzinger Straße 21 • 83278 Traunstein • Deutschland

  • ​+49 (861) 88 00 32 00
  • ​info@extocode.com
Datenschutz Impressum ​
Copyright © extocode GmbH
English (US) Français Deutsch Español Türkçe

We use cookies to provide you a better user experience on this website. Privacy Policy

Decline Accept