Powershell: PS Core on Mac updating on launch and setting an alias for brew cask based installs...

You can now install powershell core via homebrew on a Mac.  One thing I noticed is that it doesn't, which the pkg installers do, set an alias to launch powershell in the terminal.  Instead it installs an "app" in your applications directory to launch powershell.  Two things I wanted to accomplish:

  1. Set an alias to launch powershell in terminal
  2. Update powershell on launch.
Easiest way to go about this is simply to insert some alias into my .bash_profile.  Like so:
  1. Launch Terminal
  2. nano .bash_profile
    • or vi if that suits your fancy.
  3. alias powershellupdate="brew update; brew cask reinstall powershell; pwsh"
  4. alias powershell="pwsh"
  5. Exit [Ctrl+X] and Y to save.
Once done, I can now type either "powershellupdate" or "powershell" in terminal.  I did this approach for simplicity so I can quickly launch powershell if I don't need it to be updated or don't happen to have internet connectivity at time of launch.  Further down the line, I think I'm going to try and figure out available version prior to doing a reinstall.

VMware: vSAN Disk Group Cache Drive Dead or Error (VSAN Absent Disk)

A cache disk failed in my host taking along with it the disk group.  This is expected behavior, but for some reason, the disk group also disappeared from GUI so I couldn't decommission the disk group to basically replace the cached drive.  So, had to do it through powercli/esxcli.  Wish I took a screenshot, cause it was kind of annoying.

PowerCLI Example:

Once you've deleted the offending disk group, you can now create a new disk group utilizing the replaced cache disk and former capacity disks.

VMware: vxlan to vxlan traffic randomly fails or only works on the same ESXi host...

Here are the basics:

  • Leaf/Spine Architecture (Basic illustration only show ToRs)
    • Basic Illustration for explanation purposes
  • vSphere 6.5U1 / vSAN 6.6
  • NSX 6.3.3
    • Multi-VTEP Deployment w/ LoadBalance-SRCID
    • Standard VLAN for VTEP connections.
  • 2x Nexus 9K ToRs
  • Dell R630's
Long story short, Switch vPC's were stripping VLAN ID info before sending to peer ToR then to ESXi host.  ESXi host dumped it causing these strange issues.  Load Balance SrcID w/ Multi-VTEP made this especially difficult to figure out because of the basic randomness.  Switch vPC link has a configuration advantage, so in order to keep it, we ran additional links between the switches to make some standard trunk connections.  Once done, we configured our NSX VTEP VLAN network to traverse those trunk connections rather than the vPC.  This resolved our stripping issue.

See past page break for tools and more details on what we (mostly vmware NSX senior support staff) did to figure this out.
[FYI: Cisco recommendations appear to be only to use vPC between switches if the downstream host links utilize port channel (LACP) as well.  There are factors in play in the larger scheme of the network fabric, but this is from the viewpoint of a compute engineer.]

VMware: Integrating OpenLDAP into SSO/PSC over LDAPS

Quite simply was trying to get an OpenLDAP identity source added to SSO/PSC.  Would work fine using non-secure LDAP, but seemed to have issues when attempting to utilize secure LDAPS.  Simple error, nondescript basically describing that it failed.

Heres what happened in my case:

  1. I had two server URL's defined for my target LDAP servers.
    • OpenLDAP Config Screen
  2. Since I had the "Protect LDAP communications..." box checked, the next step requires me to either upload the target system's certs and their authoritative chains (think Root Certificate Authority (CA) and Intermediate CA's)
    • If you can, uploading the needed certs would save some time, otherwise you can continue w/ my outlined steps below assuming the spyglass icon works in the same fashion for you.
  3. The cert upload screen has a little spyglass icon that'll pull it down for you, but in my case it would only pull the primary server's cert and associated CA certs.  It would not pull the secondary for some reason.
  4. If I went forward anyway at this point, it would fail.  So I went back a screen, and flipped primary and secondary URL entries, then back to the cert upload screen and hit the spyglass icon again.
  5. Interestingly it pulled the secondary's (now that it was primary) cert now w/ the same associated CA.
  6. I deleted the duplicate CA entry, went back and flipped the primary and secondary back, and finished the wizard successfully.
    • Cert Upload Screen

Misc: Fire TV Stick 2 Screen Cut Off, no display adjustment option

Long story short, Fire TV Stick (2nd Generation) doesn't allow you to calibrate the screen, software wise, forcing you to use your TV settings (if available) to fit the screens content within it's borders.  Super annoying for some apps, but you can fix this dumb issue as I was able to.

If your TV allows you to adjust its settings, then you'd be fine as well, but the Vizio I have, has no such setting.

  • First you have to enable ADB debugging (step 1 here) on your fire stick.
  • Next you'll need the ADB provided w/ Android Studio, or you can install w/ brew on the Mac.
    • I prefer brew cause it's easier, keep following steps described by Amazon page if you are using Windows.
    • Open Terminal
    • brew cask install android-platform-tools
  • Next find the IP address of your Firestick
    • Settings --> Device --> About --> Network
Steps after ADB is installed:
  1. Connect to your fire stick using adb
    • adb connect <IPAddressofYourFireStick>
    • For example: adb connect
  2. If successful, you should see a return of something like this:
    • connected to <IPAddressofYourFireStick>:5555
  3. Now to adjust, these settings worked for my Vizio VX32L:
    • adb shell wm overscan 65,40,60,28
      • This is what the values stand for:
      • wm overscan LEFT, TOP, RIGHT, BOTTOM-Margin
  4. To see the changes you have reboot the stick:
    • adb shell reboot
  5. To verify after reboot go to:
    • Settings --> Display & Sounds --> Display --> Calibrate Display
  6. Repeat Steps 1-5 until your display is calibrated to your particular TVs personality.
Last comment by AmazingNick is what helped get me on the right path.