<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>nd on next-hop-self</title>
    <link>http://next-hop-self.it/tags/nd/</link>
    <description>Recent content in nd on next-hop-self</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 20 Nov 2026 09:00:06 +0100</lastBuildDate><atom:link href="http://next-hop-self.it/tags/nd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DC - ND - Nexus Dashboard Pre-upgrade validation tool </title>
      <link>http://next-hop-self.it/posts/dc-nd-nexus-dashboard-pre-upgrade-validation-tool-/</link>
      <pubDate>Fri, 20 Nov 2026 09:00:06 +0100</pubDate>
      
      <guid>http://next-hop-self.it/posts/dc-nd-nexus-dashboard-pre-upgrade-validation-tool-/</guid>
      <description>A few months ago (August 2026), Cisco released a new Nexus Dashboard major version, and we are getting close to the first starred release in the 4.x train. In this scenario, if you are planning to upgrade your Nexus Dashboard cluster from 3.2.2m (the current starred release) to 4.3.1 (the latest available version), the main question is: how can you do it safely?
Joe LeBlanc, a Cisco Technical Leader in Data Center Networking, helps us answer this question with a straightforward script published on his GitHub repository.</description>
    </item>
    
  </channel>
</rss>
