Click here to learn more
1. When configuring the “Cisco ISE” Gigabit 0 interface with either the 10.10.12.16/24 or 10.10.10.3/24 addresses it didn’t provide me more PORT-GROUP option that: VM NETWORK, DMZ and NAS (no Mngt VLAN).
With the 10.10.12.16/24 IP address, I cannot ping the Esxi (10.10.10.2): network unreachable
With the 10.10.10.3/24 IP address, I cannot ping the Esxi (10.10.10.2): destination host unreachable
When “Testing the Management Network” by pinging the 10.10.10.13 ip address from Esxi: failed (I really don’t understand why I can’t ping this addresse)
My opinion is because I have only one RJ45 port for the Management VLAN (vmk0) and I configured only one “NIC VMkernel”.
Question: is possible to add anothers (2 or 3) network adpators on the HP xw8400 Workstation ? By replacing the network card or finding an equipement ?
2. When configuring the ISE VM, I hadn’t started the DNS VM and I setup the “DNS 1” and “DNS 2” addresses with a default DNS domain name “demo.com”.
Result: the Cisco ISE VM doesn’t appears into the DNS 1 “demo.com” zone.
I am asking to re-install the “ISE VM” with the DNS server up and running before. It could explain why I cannot ping the Esxi because it has no domain configured and it is in another VLAN (10.10.10.0).
3. I cannot upgrade the “HP xw8400” Esxi to the VMware 6.5 version because the CPU model does not allow me.
Question: I there a means to perform it anyway ? Overclocking or something else ?
In advance I thank youi very much for your attention and for your help.
I think they are not reachable by ping because they are on different subnets since you configured it to be /24 mask.
You could add network adapters but I think that is not the problem at hand but just the way your vSwitch has been configured.
But if you insist on procuring additional network adapter make sure they are supported out-of-the-box by the ESXi 6.0 by checking the Compatibility Guide.
VMware Compatibility Guide – I/O Device Search and selecting “Network” device type.
Not familiar with Cisco ISE VM but I suspect it has to do with the misconfigured subnets
The Xeon 5160 processor is only qualified up to ESXi 6.0
The Xeon 5160 processor is quite old and it doesn’t have Extended Page Table (EPT) feature which makes VMs run faster in certain memory-intensive situations. EPT is also required for VMX Unrestricted Guest feature which essentially allows VMs to run nearly bare metal with minimal intervention from the hypervisor software. EPT is probably a required feature of ESXi 6.5.