endriopettini Tracker

Re: ESXi multiple networks - different DHCP scope

endriopettini — Sun, 10 Sep 2023 10:52:38 GMT

To have your endpoints automatically use your Windows Active Directory (AD) server (192.168.1.86) as the DNS1 server, you would typically need to configure your DHCP server to provide the AD server's IP address as the DNS server to DHCP clients. Since your router is currently handling DHCP, you would need to configure DHCP options on your router.

Here are the steps to configure DHCP options on many routers:

1. Access your router's web-based management interface. You usually do this by entering the router's IP address (often 192.168.1.1 or similar) in a web browser.

2. Log in to the router's administration console using the router's username and password.

3. Locate the DHCP settings. This might be under a "LAN," "Network," or "DHCP Server" section, depending on your router's firmware.

4. Look for an option to specify DNS servers. You may need to set the primary DNS server to the IP address of your AD server (192.168.1.86).

5. Save your changes and restart the DHCP service on your router if necessary.

By configuring your router's DHCP server to provide the AD server's IP address as the primary DNS server, your endpoints should automatically use the AD server for DNS resolution when they obtain their IP addresses via DHCP.

Regarding your question about VMware ESXi, ESXi itself doesn't handle DHCP services or DNS settings for endpoints unless you have a specific DHCP server running within a virtual machine on the ESXi host. However, if you want to isolate a group of VMs within a specific vCenter folder and have them use different network parameters, you can achieve this through network segmentation:

1. **Create a Separate Port Group**: In your vSphere environment, create a separate port group within your vSwitch or Distributed Switch. Assign this port group to the VMs you want to have different network parameters.

2. **Configure DHCP**: If you want these VMs to use different DHCP settings, configure a DHCP server within this isolated network segment (port group). You can run a DHCP server on a VM within this segment, or if your router supports multiple DHCP scopes, configure a separate scope for this segment.

3. **DNS Configuration**: For DNS settings, you can either configure them manually on the individual VMs or configure the DHCP server in this segment to provide the desired DNS server IP addresses.

By segmenting your network in this way, you can have specific VMs use different network parameters while still being part of the same ESXi host and vCenter environment.

Re: Connecting ESXi hosts to 17 or more vDS

endriopettini — Sun, 10 Sep 2023 10:50:51 GMT

In a VMware vSphere environment, connecting an ESXi host to more than the recommended maximum of 16 VMware Distributed Switches (vDS) can lead to unexpected behavior and is generally not a supported configuration. The maximum limit of 16 vDS per host is defined for various reasons, including management and resource allocation considerations.

While some of these vDS may not have active physical uplinks, they are still part of the host's configuration and consume resources such as memory and CPU cycles. Going significantly beyond the recommended limits can potentially lead to performance issues, management complexity, and unintended consequences.

While it may be technically possible to connect an ESXi host to more than 16 vDS by creating additional vDS with no active physical uplinks, doing so is not advisable from a best practices standpoint. VMware recommends adhering to the documented configuration limits to ensure stability and predictability in your virtualization environment.

If you find yourself in a situation where you believe you need to exceed these limits for a specific use case or requirement, it's a good idea to reach out to VMware support or consult with a VMware representative for guidance. They can provide insights into whether there are alternative solutions or configurations that can meet your needs while staying within supported limits.

Re: VXLAN without NSX

endriopettini — Sun, 10 Sep 2023 10:49:24 GMT

In a VMware vMSC (vSphere Metro Storage Cluster) setup using VXLAN for network virtualization and spanning multiple datacenters with Cisco Catalyst switches and ISL (Inter-Switch Link) connectivity, you can indeed configure VXLAN without VMware NSX by relying on the capabilities of the physical network switches. Below are the key steps you would typically need:

1. **VXLAN Configuration on ESXi Hosts**:

- Ensure that ESXi hosts in both datacenters have VXLAN enabled and are running compatible versions of VMware vSphere.

- Create and configure a VMware Distributed Switch (VDS) that spans both datacenters. This VDS will be used for VXLAN traffic.

2. **Distributed Switch Configuration**:

- Create a Distributed Port Group on the VDS specifically for VXLAN traffic.

- Enable IGMP Snooping on the Distributed Switch if required for multicast group management (which is common in VXLAN deployments).

3. **Physical Switch Configuration**:

- On the Cisco Catalyst switches, enable VXLAN support, which typically involves configuring the following:

- VLANs: Ensure that the VLANs used for VXLAN are properly configured on the switches.

- Multicast Support: Configure multicast group addresses for VXLAN traffic and ensure proper multicast routing if needed.

- MTU Size: Ensure that the MTU size is consistent across your entire network, including both ESXi hosts and physical switches. VXLAN adds encapsulation, so you might need a larger MTU size.

- ISL Configuration: As you mentioned, you have ISL between datacenters. Ensure that ISL is correctly configured to allow VXLAN traffic to traverse between the datacenters.

4. **VTEP Configuration (VXLAN Tunnel Endpoints)**:

- Configure Virtual Tunnel Endpoint (VTEP) interfaces on the physical switches. These interfaces are responsible for encapsulating and decapsulating VXLAN traffic as it enters and exits the physical network.

5. **VXLAN Segment Configuration**:

- Define VXLAN segments or VNIs (VXLAN Network Identifiers) as needed to segment your network. Each segment represents a separate logical network on top of the physical infrastructure.

6. **Routing Configuration (if required)**:

- If you need to route traffic between VXLAN segments or VNIs across datacenters, you'll need to configure routing on the physical switches.

7. **Testing and Validation**:

- Thoroughly test your VXLAN setup to ensure that traffic flows as expected between virtual machines in different VXLAN segments and across datacenters.

8. **Monitoring and Troubleshooting**:

- Implement monitoring and logging to assist in troubleshooting and maintaining the VXLAN network.

Remember that VXLAN configurations can be complex, and they should align with your specific network design and requirements. It's also crucial to consult the documentation for your Cisco Catalyst switches and follow best practices provided by VMware for VXLAN deployments in a vMSC environment.

Re: VDS Load Balancing for LAG / LACP

endriopettini — Sun, 10 Sep 2023 10:46:42 GMT

It depends heavily on your environment; if your traffic is primarily at the L2 level, it makes more sense to use the MAC-based algorithm as it involves one less level of processing. Some devices offer the option to use both IP and MAC, which is another way to effectively balance traffic for both layers of the OSI model (L2 and L3).

Re: NSX ISP

endriopettini — Sun, 10 Sep 2023 10:33:06 GMT

O VMware NSX é uma plataforma de virtualização de rede que oferece recursos avançados de rede virtualizada e segurança para data centers e ambientes de nuvem. Em um ambiente de provedor de serviços de Internet (ISP), a função principal do NSX pode ser fornecer serviços de rede virtualizados para clientes, melhorar a segurança da rede e simplificar a operação da rede. Aqui estão algumas das principais funções do NSX em um ambiente ISP:

1. **Virtualização de Rede**: O NSX permite que os ISPs criem redes virtuais isoladas para cada cliente ou grupo de clientes. Isso ajuda a segmentar o tráfego e garantir que os clientes não interfiram uns nos outros.

2. **Gerenciamento de VLAN**: O NSX pode ser usado para criar redes virtuais usando VLANs, o que ajuda na segmentação de tráfego e na atribuição de VLANs específicas a clientes ou serviços.

3. **Roteamento Virtual**: O NSX oferece recursos avançados de roteamento virtual, permitindo que os ISPs configurem rotas personalizadas para seus clientes e otimizem o tráfego na rede.

4. **Firewall Virtual**: O NSX inclui um firewall virtual que pode ser usado para aplicar políticas de segurança em nível de aplicativo, segmentando e protegendo o tráfego de clientes contra ameaças.

5. **Balanceamento de Carga Virtual**: O NSX suporta balanceamento de carga virtual, que pode ser útil para distribuir o tráfego entre vários servidores ou recursos de clientes.

6. **Isolamento de Ambiente**: O NSX ajuda a isolar os ambientes de clientes uns dos outros, aumentando a segurança e evitando conflitos de IP ou problemas de segurança.

7. **Orquestração e Automatização**: O NSX geralmente é integrado a ferramentas de orquestração e automação, o que permite que os ISPs provisionem e gerenciem facilmente recursos de rede para clientes sob demanda.

8. **Monitoramento e Visibilidade**: O NSX oferece ferramentas de monitoramento e visibilidade que permitem aos ISPs acompanhar o desempenho da rede e identificar problemas rapidamente.

9. **Recuperação de Desastres**: O NSX também pode ser usado para configurar soluções de recuperação de desastres, como replicação de máquinas virtuais e failover de rede para garantir alta disponibilidade dos serviços de rede.

Em resumo, a principal função do VMware NSX em um ambiente ISP é virtualizar e automatizar a rede para oferecer serviços de rede flexíveis, seguros e escaláveis para os clientes, ao mesmo tempo em que simplifica a operação e a gestão da rede.

Re: Implementação de NSX

endriopettini — Sun, 10 Sep 2023 10:29:01 GMT

Excelente post.

Vai me ajudar muito.

Re: Problemas NSX

endriopettini — Sun, 10 Sep 2023 10:26:52 GMT

Falha de operação de MTU e VXLAN entre vendors.