NSX-T – Inline and One-Arm Load Balancing Part 1


I’ve been a user of NSX-T for a while but as I’m not a networking guru I know just enough to get the job done (and enough to be dangerous) but not enough to design a large scale setup. Load balancing is something that I haven’t really paid much attention to, I just accepted that it works.

With vRA8 coming ever closer to GA and our internal pre-GA software doing the rounds within VMware I needed a load balancing configuration to test a few scenarios out. The NSX-T 2.4 (and previous 2.x versions) documentation is pretty ambiguous when it comes to explaining the various load balancing configurations you can deploy (one-arm and inline). It covers the concepts of each type of deployment at a VERY high level but it doesn’t actually explain how the different configurations need to be implemented.

In this mini series of articles I am going to…

View original post 823 more words


NSX-T – Inline and One-Arm Load Balancing Part 2


In part 1 of this mini-series I looked at how you implement a one-arm load balancing solution using NSX-T (https://vnuggets.com/2019/09/13/nsx-t-inline-and-onearm-load-balancing-part1/). In this second part I am going to switch focus to look at the inline implementation so you can see how the required components and configuration differs.

Logical Architecture

As a reminder from part 1, here is the logical architecture for an inline load balancing implementation with NSX-T (for a side by side architecture comparison view check out part 1).

Inline Configuration

The starting network configuration taken from the above diagram will be External -> T0 -> T1 -> Segment2. This is utilising the same routers as I did in part 1, this time with a new segment (“Segment2”) and associated subnet for the pool of load balanced machines to connect to.

The key thing to understand with an inline configuration is that the load balancing interface…

View original post 412 more words

Mac: NFS Mount set to read-only

Recently I had an old external drive I wanted to mount use as a backup target, unfortunately when mounted it was set to read-only to resolve this i used the following  packages and commands : 

Write to an NTFS Drive With NTFS-3G:
Pre-Req: the following packages require installation, using brew :

  • #brew install ntfs-3g
  • #brew cask install osxfuse

NTFS-3G enables your Mac to write to NTFS drives, 
First, find the address of your mounted read-only drive, using the command:

#diskutil list

Before you try to mount the new volume, you need to unmount the existing read-only NFS drive, otherwise you will get the following:

  • Error opening ‘/dev/disk3s1’: Resource busy
  • Failed to mount ‘/dev/disk3s1’: Resource busy
  • Mount is denied because the NTFS volume is already exclusively opened.
  • The volume may be already mounted, or another software may use it which could be identified for example by the help of the ‘fuser’ command

#sudo umount /Volumes/YOURDRIVE/

You need to run the following commands each time that you want to mount a drive with write permissions.

Replace /dev/disk1s1 with the drive address that you found above:

#sudo mkdir /Volumes/NTFS
#sudo /usr/local/bin/ntfs-3g /dev/disk1s1 /Volumes/NTFS -olocal -oallow_other

Error: I received the following error on first run:

  • dyld: Library not loaded: /usr/local/lib/libosxfuse.2.dylib
  •   Referenced from: /usr/local/bin/ntfs-3g
  •   Reason: image not found, 

The Fuse library had an issue, I had an older version of fuse installed, so I reinstalled with: #brew cask reinstall osxfuse

If you don’t want to run these commands each time, there’s a fix.
You can boot your Mac into single-user mode, and replace the built-in Mac NTFS tools with NTFS-3G.
There are some warnings about security on the project site; you can check out the steps to enable it on the developer’s GitHub page.
The devs make it clear that this opens up your Mac to potential exploitation, so this step is not for the faint of heart.


Ref :https://www.makeuseof.com/tag/self-hosted-read-later-app/