Possibly my longest title ever? As the intro says this is a bit of roleplay for us, we are setting up the lab as a Managed Service Provider (MSP) who wishes to have a way to tunnel in (or in this case have the client tunnel out) to HQ where we can monitor all the goodies that PRTG can monitor remotely.
Part 2 Setup of connectivity Setup OpenVPN Server with client specific info Setup OpenVPN Client Using Easy-RSA to generate certificates and keys Securing interfaces with Firewall Securing vtun0 interface with firewall
As ever I try and bring you guys (and girls?) something a little different :) After completing this video here and being in contact directly with PRTG it came to my attention that the version I was using "PRTG Traffic Grapher V6" was EOL and the new version "PRTG Network Monitor" is the successor. Network Monitor does have alot of cool new features including an iPhone app (cant wait for a droid version) and the best bit...they were kind enough to provide me with a copy of PRTG Network Monitor V7 for this video.
Part1 A cool tour of some of the features of PRTG Network Monitor V7 and how we use our virtual machine to monitor our voice network
So its almost coming up for a year since I really gave this blogging thing ago, it reminded me of my first videos, back when I was using VMware's built in tools to record video (which actually are not that bad!) however on my travels I bumped into this article here
Windows 2003 Clustering with EMC Celerra VM -Part1 In this video we do the majority of the setting up from domain controller to iSCSI LUN masking, its all here! Some Commands you might find handy: Change hostname /etc/host - new ip address hostname /etc/sysconfig/network - domainname=cookie.local
Part 3 Configuring Fencing, Failover Domain, Resources and Services. Helpful Commands: Configure Resources: IP GFS Samba
Configure failover Domains
Configure Shared Fencing Device (then nodes)
Add Services
workgroup = cookie server string = Samba Server Version %v bind interfaces only = yes interfaces = 10.0.1.100 netbios name = cluster1 local master = no domain master = no preferred master = no password server = None guest ok = yes guest account = root security = SHARE dns proxy = no
[sanvol] comment = High Availability Samba Service browsable = yes writable = yes public = yes path = /san/sanvol1 guest ok=yes create mask=0777
As we all know compliance is one of the biggest issues facing companies at the moment leading some IT departments to take a look at 802.1x as a way of controlling and securing access to their wired networks.
The main reason for this post is there are a few articles out there that have mis-truths and incorrect facts within them, often due to them having not implemented the technologies themselves.
Here is the lab:
So here we go: Part1 GNS Setup VMware Workstation Setup Domain Controller Setup