<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on NPetersen</title><link>/tags/networking/</link><description>Recent content in Networking on NPetersen</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 06 Sep 2022 00:10:00 +0100</lastBuildDate><atom:link href="/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>NSX Troubleshooting, what changed in the firewall?</title><link>/posts/nsx-what-changed/</link><pubDate>Tue, 06 Sep 2022 00:10:00 +0100</pubDate><guid>/posts/nsx-what-changed/</guid><description>&lt;p&gt;I found a neat feature that I didn't know in the NSX Manager during a late night.
Every publish/change makes a configuration point, that you can see what changed from then -&amp;gt; now.&lt;/p&gt;
&lt;p&gt;This can be good for troubleshooting, something that stops working, that might be due to a DFW Configuration issue.&lt;/p&gt;
&lt;p&gt;Go to the DFW, over the categories click &amp;quot;Actions&amp;quot; -&amp;gt; Under Drafts click &amp;quot;View&amp;quot;
You will be presented with the saved configurations:&lt;/p&gt;
&lt;p&gt;&lt;a href="/img/NSX-T_DFW-FWChanges.png"&gt;&lt;img src="/img/NSX-T_DFW-FWChanges.png" alt="NSX-T DFW Changes"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;So lets go into troubleshooting mode, and lets say something stopped working at 10:32. I can find the date in the above screenshot and point at the dots and see the timestamps - look below:&lt;/p&gt;</description></item><item><title>NSX-T 4.0.0.1 - Whats new?</title><link>/posts/nsxt-40/</link><pubDate>Wed, 17 Aug 2022 00:10:00 +0100</pubDate><guid>/posts/nsxt-40/</guid><description>&lt;p&gt;In NSX-T 4.0.0.1, VMware changed their naming scheme (again, would some say), to just be NSX.
One of the biggest features, and long overdue is IPv6 support for management. There is also a new feature for Blocking Malicious IPs, which we will look at below.&lt;/p&gt;
&lt;p&gt;Here are the Release Notes: &lt;a href="https://docs.vmware.com/en/VMware-NSX/4.0/rn/vmware-nsx-4001-release-notes/index.html"&gt;https://docs.vmware.com/en/VMware-NSX/4.0/rn/vmware-nsx-4001-release-notes/index.html&lt;/a&gt;&lt;/p&gt;
&lt;h1 id="block-malicious-ips"&gt;Block Malicious IPs:&lt;/h1&gt;
&lt;p&gt;In the Release Notes the following is written:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Block Malicious IPs in Distributed Firewall is a new capability that allows the ability to block traffic to and from Malicious IPs.&lt;/li&gt;
&lt;li&gt;Block Malicious IPs in Distributed Firewall is a new capability that allows the ability to block traffic to and from Malicious IPs. This is achieved by ingesting a feed of Malicious IPs provided by Vmware Contexa. This feed is automatically updated multiple times a day so that the environment is protected with the latest malicious IPs. For existing environments the feature will need to be turned on explicitly. For new environments, the feature will be default enabled&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;My LAB enviorment is a existing installation, so it will need to be turned off explicitly as the release notes says. Luckily thats quite easy in NSX-T.&lt;/p&gt;
&lt;p&gt;We also know its a part of VMware Contexa, that is VMwares take on a cloud security platform. I actually didnt know about Contexa before this update, it looks cool. We might see more of Contexa in later NSX-Releases, maybe within NSX-Intelligence where more of the Contexa looks to be already.&lt;/p&gt;
&lt;h2 id="lets-setup-auto-update"&gt;Lets setup auto update:&lt;/h2&gt;
&lt;p&gt;As you can see below, you will right away after upgrading the NSX-T Manager to 4.x the warnings telling you:
&lt;em&gt;Auto Update Malicious IPs is turned off. All rules containing groups with malicious IPs might not work at all or work with outdated data if available.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/img/NSX-T_DFW-Warnings-MaliciousIPS.png"&gt;&lt;img src="/img/NSX-T_DFW-Warnings-MaliciousIPS.png" alt="NSX-T DFW Warnings"&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>High latency for VMs in NSX-T (VLAN)</title><link>/posts/highlatencynsxt/</link><pubDate>Mon, 15 Aug 2022 00:02:00 +0100</pubDate><guid>/posts/highlatencynsxt/</guid><description>&lt;p&gt;NSX-T Version: 4.0.0.1.0.20159689&lt;/p&gt;
&lt;p&gt;I was experiencing a high latency in NSX-T for all my VMs, and i couldnt figure out why. VMs on the same host, that wasnt on a NSX-T segment had +90ms in latency.
I was pinging from a VM on VLAN 10 to a VM thats part of my NSX environment on VLAN 20. Both VMs was on the same host, and I dont have any NSX-T Overlay routing, so it was kinda weird.&lt;/p&gt;
&lt;p&gt;Let me first show you how the latency was fluctuating:
&lt;img src="/img/NSX-T_latency_issue.png" alt="NSX-T high VM latency"&gt;&lt;/p&gt;
&lt;p&gt;As you can see above the latency was in the low end at 8ms and to the very high end of 150+ ms per ping. Thats not acceptable, and especially not when the VMs are on the same host, and there is only 1 router between the VLANs.&lt;/p&gt;</description></item></channel></rss>