El conocimiento al alcance de todos.

Thanks to:  https://blogs.technet.microsoft.com There is a lot of information about NPIV out there on the internet (What it is, how it works, what are the prerequisites of NPIV etc)  In this blog I am only focusing on the Implementation of  NPIV in Windows Server 2012 For the Simplicity of configuration and Demonstration I have not Clustered the Physical Host Machines, instead made use of the HyperV  replication feature to Failover the VM from one node to another node. Equipment Used Servers: Two Dell PowerEdge 860’s OS: Windows Server 2012 Datacenter  (RTM) HBA’s: Emulex A8003A Dual Port HBA Firmware:2.82A4 HBA Driver version: 2.72.012.001 Fabric Switch: Brocade 300 Fabric OS: v6.4.2a Storage: HDS HUS110    Naming Convention Followed Physical Hosts: Contoso76, Contoso77 Virtual Machine:Contoso80 Domain Name:contoso7x.local Brocade Switch: HDS_Switch1 & HDS_Switch2 Design Configuration Steps 1. Open the Emulex One command utili

Thanks to: https://araihan.wordpress.com Windows Server 2012 R2 with Hyper-v Role provides Fibre Channel ports within the guest operating system, which allows you to connect to Fibre Channel directly from within virtual machines. This feature enables you to virtualize workloads that use direct FC storage and also allows you to cluster guest operating systems leveraging Fibre Channel, and provides an important new storage option for servers hosted in your virtual infrastructure. Benefits: Existing Fibre Channel investments to support virtualized workloads. Connect Fibre Channel Tape Library from within a guest operating systems. Support for many related features, such as virtual SANs, live migration, and MPIO. Create MSCS Cluster of guest operating systems in Hyper-v Cluster Limitation: Live Migration will not work if SAN zoning isn’t configured correctly. Live Migration will not work if LUN mismatch detected by Hyper-v cluster. Virtual workload is tied with a single Hy

Thank to: http://www.techtutsonline.com/ In this section, we will discuss about configuring two VPN tunnels on the same router interface. This configuration is required if you have two branch offices at different locations and you want to connect each branch office to head office. I will use the following network diagram for demonstration: Consider that your company’s head office is located in Delhi (India) and Router R1 is your head office router connected to ISP via high speed link. The R2 and R3 routers are located in Sydney and Singapore respectively. You want to establish an IPsec VPN tunnel so that the private LAN connected behind R1 (192.168.10.0/24) can access the private LAN behind R2 (192.168.20.0/24) and R3 (192.168.30.0/24) and vice versa. I will assume that basic network configuration is already done. All the routers are assigned a public IP address on outside interface and every router can ping each other since they are connected to internet. Configuration of