Private VLANs (PVLAN)

VLAN provides network isolation and layer 2. Typical VLAN would have a single subnet and all the devices within the VLAN can communicate with each other. But what if you want to put multiple devices within a subnet and do not wish to communicate with each other ? The answer would be the use of Private VLANs (PVLANs).

How it works

PVLANs are actually a set of VLANs. There is a Primary VLAN and one or more Secondary VLANs. 

Primary VLAN – Same as a typical VLAN and the networks are promiscuous, as they will always communicate with each other

Secondary VLAN – These networks are associated with the Primary VLAN and they keep seperated with each other

In Secondary VLANs, there are two types of Networks 

  • Community VLAN – In a community VLAN, the devices will communicate with each other. But the Inter community VLAN does not take place. [ex: Community A and Community B VLANs will have no communication]
  • Isolated VLAN – In an Isolated VLAN, the devices will not communicate with each other. They also have no Inter commuication with Community VLANs.

All the devices can connect to the Primary VLAN. So this allows the devices to share Internet connectivity. Basically, this will act as the default gateway. 

Ports in the Primary VLAN are known as the Promiscuous Ports (P-Ports). Layer 3 switches are placed here and can have SVI (Switch Virtual Interface) configured in the Primary VLAN.

Ports in the Secondary VLANs are known as the Host Ports , as the name suggests these ports are being used to connect the end points (devices).

The below Diagram provides a good explanation

Continue reading “Private VLANs (PVLAN)”

Step by Step MS SQL Database Cluster configuration using SQL 2019 on Server 2022

Failover Clusters provide seamless Availability and Uptime. On failover clusters, we can run different services/applications. In general, we can run Hyper V VMs, VM Replicas, DHCP and also Database applications. A typical failover cluster consists of 2 nodes (servers), shared network and shared storage systems. 

Today, we will be looking at the exact steps in order to create a failover cluster and how to run MS SQL server on the configured cluster. 

There are some Prerequisites as mentioned below

  1. Active Directory infrastrcture
  2. AD administrator account
  3. A shared storage system (iSCSI, FCoE or FC supported protocols)
  4. 2 or more nodes (Servers)
  5. MS SQL server ISO
  6. Functional DNS server
  7. Few free IP addresses

Lets look at my setup

Server Name dc.chatz.local node1.chatz.local node2.chatz.local
Server IP 192.168.79.129 192.168.79.130 192.168.79.131
Installed Roles

Active Directory / File Server (iSCSI) / DNS

Failover Cluster Manager Failover Cluster Manager
Notes

iSCSI shares

512 MB – Witness

20 GB – Cluster Shared Volume

192.168.11.100  (for cluster heartbeat)

192.168.11.101 (for cluster heartbeat)

This process consists of 2 phases, Phase 01 would be the Cluster Creation and Phase 02 is the MS SQL DB Cluster setup.

Phase 01 – Windows Failover Cluster setup

NOTE: When working with the AD services, make sure to create an OU and place all the cluster related objects in the OU which you create. As per my setup, the OU looks like this

As the very first step, you need to install Failover Cluster role on all the participating nodes (in this example, we have only 2). Once you are done with the role installation, apply the Windows patches. And then you may finalize setting up the iSCSI shares. Finally, make sure to add all those nodes to the Active Directory Domain. 

Then, you need to add those iSCSI storage as volumes on the selected nodes. This can be done using the Disk Management console.

Once you are done with assigning the volumes, you are good to validate the cluster. You can simply access the Failover Cluster Manager role from a selected node

Continue reading “Step by Step MS SQL Database Cluster configuration using SQL 2019 on Server 2022”