Currently I have two esxi hosts. Each has two nics connected to a vswitch for all of our VMs. The VMs are spread across five VLANs that are tagged on the port groups and the two physical nics are trunk ports on the switch. Would I get better performance if I put each VLAN on its own separate vswitch with its own nic and set the physical nics as access ports on the switch?
Thanks.
Hi
Is there a way to list out all the VLAN's that the physical networkcard on ESXi can see from the switch?
esxcfg-vswitch -l only show defined VLAN's on the system.
I know HPE Oneview has presented all VLAN's to the blade, but i can only see some of them in the ESXi console. Not sure where the miconfiguration is.
I have installed both ESXi 5.1 and 6.5 to verify that it's a consistent error, and OS related.
Hello everyone!
I just purchased Cisco ASA 5506-X K9. I have two VMware ESXi 5.5 U3 (build 3568722) hosts.
Now I need to connect each host to my Cisco ASA 5506. I want to configure vlan trunk with two vlans.
Here is configuration on the ASA side:
interface GigabitEthernet1/3
channel-group 1 mode active
interface GigabitEthernet1/4
channel-group 1 mode active
interface Port-Channel 1
interface Port-Channel 1.93
description Inside Vlan93
vlan 93
nameif inside
security-level 100
ip add 192.168.3.254 255.255.255.0
interface Port-Channel 1.94
description DMZ Vlan94
vlan 94
nameif dmz
security-level 30
ip add 192.168.4.254 255.255.255.0
VMware side in configured in the same way as described in this video, but I cannot make it work (no traffic between Cisco and VMWare hosts). Please see screenshots in attachment.
I have only one difference from video manual:
Adapter Broadcom Corporation NetXtreme BCM5719
Link Layer Discovery Protocol is not available on this physical network adapter
Can somebody help me please? How to configure VMWare side properly?
Hi All,
I have 01 data center with: 01 cluster ( 02 hosts), 05 hosts belong the data center
The cluster with information as below:
+ 02 hosts belong cluster ( host 01 , host 02)
+ 01 vSphere Distributed Switch with 03 different vlan (1, 2, 3)
+ 01 virtual machine ( virtual machine A) running on the host 01, network card belong vlan 1 on vSphere Distributed Switch of the cluser.
I migrate the virtual machine A from the cluster to the single host of the data center, the singe host do not have vSphere Distributed Switch, only has standard switch and attempt error as the picture
Hello,
I'm using ESXi 6.5.0 build 4887370, vSphere Client 6.0.0 build 2502222 and VSphere Web client.
I can use and configure vSwitch on both vSphere Client and Web Client without errors or problems.
Instead I've misconfigurations because I can't see dSwitch configuration on both vSphere Client and Web Client. I'm following these guidelines:
Create a vSphere Distributed Switch
Please how can I enable dSwitch in my ESXi in order to see it on both vSphere Client and Web Client?
Thanks,
Andrea
Hello,
I have this scenario:
vSwitch0 -> vmnic0 --> physicalAppliance
|
|--> PortGroup0
| |
| |--> VirtualMachine0
| |
| |--> VirtualMachine1
|
|--> PortGroup1
|
|--> VirtualMachine2
I'd like to have that physicalAppliance'll to able to sniff all traffic generated from all VirtualMachines.
So, I've enabled Promiscuous mode on vSwitch0 (and on all PortGroups indirectly) and in this case any VirtualMachine is enabled to sniff the traffic generated from other two VirtualMachines, but physicalAppliance is not enabled. So, how can I configure vSwitch0 in order to enable port mirroring on vmnic0 (and on physicalAppliance indirectly)?
Thanks,
Andrea
Hi All,
- My situation: I have a cluster VMware with 02 host, which it have information as below:
+ Config vSphere HA
+ Host 01: 01 management standard switch: only physical adapter network
+ Host 02: 01 management standard switch: only physical adapter network
- And cluster show warming "THIS HOST CURRENTLY HAS NO MANAGEMENT NETWORK REDUNDANCY" in the 02 host
- And I resolved this message with action:
+ I added 01 physical adapter network available ( host 01 - vSphere HA state Master) this physical adapter I did not plug in to physical switch ( status physical adapter DOWN), and then I config complete, on the dashboard summary prompt message
+ And then, I remove the physical to vSwitch Management, and result is: I can not connect this host via vSphere Client, and service monitor on this host not working.
- Can you advice for me? Thank you very much
Hello Experts,
Wanted to know how unknown ethertype packets from VM are handled by DVS.
I see following stats when unknown ethertype packets are received by DVS.
esxcli network port stats get -p 83886084
Packet statistics for port 83886084
Packets received: 11525
Packets sent: 5983
Bytes received: 454766
Bytes sent: 1182070
Broadcast packets received: 4298
Broadcast packets sent: 4011
Multicast packets received: 5249
Multicast packets sent: 13
Unicast packets received: 1978
Unicast packets sent: 1959
Receive packets dropped: 0
Transmit packets dropped: 9181
Is there a option that can be enabled in DVS to forward packets on uplink instead of dropping it?
Thanks
Raja
I am using an HPE Superdomes server / ESXi 6.0 u3 , VC 6.0 u3
I want to use vDS for LACP functionality
Currently using mgmt 2 port service 4port(vSwitch1 2port / vSwitch2 2port)
Can I use all 6 ports in LACP configuration?
Is there any issue in configuration?
Is it better to organize management separately?
LACP1 mgmt 2 port / LACP2 service 4 port ?
Hi,
we would like to set up a single esxi host with 4 fNICs to work with nic teaming. Is it possible to connect e.g. fNIC3 and fNIC4 into Team (vSwitch - PortGroup VLAN tag). Then on a physical network connect fNIC3 in CiscoSwitch1 (trunk port) and fNIC4 in CiscoSwitch2 (trunk port). If so which load balancing algorithm should we use. CiscoSwitch1,2 are not in stack. Thanks
ESXi 6.0 u3 I want to set QoS on vDS
After setting in vDS
Do I have to configure the same on the physical switch?
if not
I set it only in vDS or physical switch?
Wanted to understand Uknown unicast flood in DVS.
Uknown unicast packets are sent out on first uplink even though it doesn't allow the VLANS of the packet.
VM is tagging the packet with VLAN-A and VLAN-A is not allowed on "Uplink port" but all packets are sent out of the uplink.
Is this expected behaviour?
Hi All
I'm not an absolute newbie in vmware, however I have used only standard vSwitches and failover link configuration.
Now I'm trying deploy much more complicated configuration. I have installed 5 ESXi hosts (2 NICs each) and vCenter and configured Distributed Switch. After that i have moved my physical NICs to this one and configured 5 LACP LAG (2 NICs each). So, now I have 5 port groups, each of them includes vmkernel port of one of ESXi host and setted up for using corresponding LAG. My problem is misunderstanding how to setup virtual machines portgroups correctly. Now I can only set one LAG as active (no multiple LAGs supported) for every single portgroup. What will happen if I move VM to different host?
I have searched it via google and VMWare docs, but found nothing apropriate, so I will be grateful for any peace of advices or theoretical info or best practices references about this topic.
hi guys
I have a recent doubt that might be simple but this will help me to clarify
I have this environment and I am sure you can not get more than 1GB link speed - transfer rate abot 100MBps to 130MBps - so here it goes just to confirm with you
one of these days someone tell me hey why if the link is 4GB since we have 4 nics and LACP/etherchannel configured when working on this project the transfer rate we get is only like 125MBps we are suppose to get about 400MBps....
I explained that IP hash will theoretically help when connecting one to many so it take advance of the multiple uplinks but not more than the uplink which is 1GB per card
I already said to them if you need more speed you have to match your external physical servers with 10GB uplinks too
so is this configuration wrong? is Enhanced LACP not configured correctly?
or I am correct and of course how I VM will send more than the uplink 1GB ia capable
but when reading this I am not good at explaining to my customer
Any virtual machine can use any uplink in the NIC team depending on the source and destination IP address. In this way, each virtual machine can use the bandwidth of any uplink in the team. If a virtual machine runs in an environment with a large number of independent virtual machines, the IP hash algorithm can provide an even spread of the traffic between the NICs in the team. When a virtual machine communicates with multiple destination IP addresses, the virtual switch can generate a different hash for each destination IP. In this way, packets can use different uplinks on the virtual switch that results in higher potential throughput
thanks a lot
Need help configuring Link aggregation between an ESXI 6.0 host and an Alcatel- Lucent OS6450-P48 switch.
What I have done.
ESXI Host:
Vswitch0
Load balancing: Route Based on IP hash
Network Failover Detection: Link status only
Notify Switches: Yes
Failback: Yes
Active Adapters: vmnic0-3
Alcatel-Lucent Switch:
I have tried both Static and Dynamic
Static:
static linkagg 2 size 4
static agg 1/23 agg num 2
static agg 1/24 agg num 2
static agg 1/25 agg num 2
static agg 1/26 agg num 2
vlan 55 port default 2
Dynamic:
lacp linkagg 2 size 4 actor admin key 5
lacp agg 1/23 actor admin key 5
lacp agg 1/24 actor admin key 5
lacp agg 1/25 actor admin key 5
lacp agg 1/26 actor admin key 5
vlan 55 port default 2
I have also tried configuring the link aggregation group "2" to trunk vlan 55 but it didn't change anything.
Currently, if I just have my regular config on my switch and plug all 4 wires in then I can still get to the ESXI host but I don't think it is doing any load balancing over the 4 cables. Once I configure static or dynamic link aggregation on the physical Alcatel- Lucent switch I can no longer get to the ESXI host unless I unplug all but 1 cable.
I have esxi 6.0 4192238 . I created a Distributed Switch distributed port group . By default, Promiscuous Mode is Reject. MAC Address Changes and Forced Transmits are Accept.
but vmware says different policy . why is different ?
Hi all,
Following is the situation:
We are using an ESXi host for demo purposes with direct-attached storage. To be able to create extra data-stores we have directly attached a NetApp system to serve as NFS server. The reason we attached the NetApp directly to ESXi host is the lack of available switch ports.
There is a default TCP/IP stack with 172.16.x.x network. I have added a new TCP/IP stack for NFS traffic (192.168.100.0/24). I created a new standard vSwitch with VMkernel port (vmk1) for NFS traffic. The VMkernel port has IP-address 192.168.100.101. I have also added the vmnic which is attached to NetApp port to the new vSwitch. For some reason I cannot get traffic to 192.168.100.0/24 to go through VMkernel port vmk1. I cannot add a static route because I have no default gateway for this subnet.
NetApp data-lif serving NFS has IP-address 192.168.100.100. From the NetApp data-lif I can reach (ping) the address of the VMkernel port vmk1 (192.168.100.101).
But a traceroute from ESXi shell to NetApp data-lif 192.168.100.100 tries to connect through VMkernel port vmk0 (172.16.x.x).
Can someone please share some light on this....or perhaps point me in the right direction?!
Thanks in advance!
Rob
Hi,
I am trying to upgrade vCenter from 5.5 to 6.5 using command line but during precheck my script is showing IP instead FQDN and below warning when I check hostname I see FQDN.
I still no clue what is the reason.
Pre-upgrade check warning: 1. Title: Host name 192.168.xx.xx is not DNS
resolvable, but matches the machine certificates. If you do not configure a
valid DNS resolvable hostname mapping, then you might not be able to connect to
the vCSA afterwards
Hi there!
Soon we'll finally have 10GbE with our new ESXi hosts and I'm wondering how I should set up the different vSS (and probably vDS next year after the planned upgrade) to get the best out of speed and redundancy. The hosts will have 2x 10GbE (on 1 NIC) and 4x 1GbE (those are onboard and guaranteed to be on 1 NIC, too).
The current hosts have 6x 1GbE on two NICs, where one of each NIC is in a vSwitch for the vMotion (vmk0) and management (vmk1) adapter. The remaining 4 are on another vSwitch for the VMs. All physical ports are active. We use NFS which is in the same subnet as vmk0.
I have no good idea how to use the 10GbE with the 1GbE ports. First, I'll probably create a new vmk for the NFS traffic*, or is it okay to run those two in the same VLAN like we do now? After the migration to the new hosts we will have a maximum of 3 hosts.
Then I'll either put 1 or 2 1GbE into the first vSwitch for the management vmk adapter and the rest into another vSwitch. There the 10GbE adapters will both be active and the 1GbE adapters will be on standby.
Would this be a valid and and good way to distribute the physical ports into the hosts and VMs? The physical switch on the other side is of course stacked and I'll connect to it in a redundant fashion like we do already.
Kind regards,
Chris
*I'll probably just create new vMotion NICs so I don't have to change anything on the storage side, just create a new VLAN and Subnet for vMotion
Hi,
I recently upgraded vCenter and ESXI 5.5 to 6.5 and upgrade was successful. I deployed some new VMs on upgraded ESXI hosts but when I try to power on I am getting error "The host is reporting errors in its attempts to provide vSphere HA support.”"
When I turned off the HA on cluster and try to power on new VM then I get error “The available Memory resources in the parent resource pool are insufficient for the operation.”
The odd thing was, there were no resource pools that had been setup. Nothing was reserved for any VM.