Posts

Showing posts from March, 2020

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
Summary:
I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up.

PreReqs:
HomebrewInstalling OpenConnect:
Launch MacOS Terminal brew install openconnectGetting VPN IP's/DNS Endpoints from AnyConnect:
The information is typically located in your profile xml files located here:
/opt/cisco/anyconnect/profile/somethingsomething.xml

In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnect.

Using OpenConnect:
For the sake of simplicity right now, you would now just type in your MacOS Terminal:
openconnect https://typicallyaDNSName.com Depending upon t…

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary:
NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine.

So what's going on here? 
This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown.

Workaround:
Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI.


Details:
If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face and get nowhere because another node is actually responsible f…