<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>vBond on AxelRobbe.nl</title>
    <link>https://blog.axelrobbe.nl/tags/vbond/</link>
    <description>Recent content in vBond on AxelRobbe.nl</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Jun 2021 10:29:15 +0100</lastBuildDate><atom:link href="https://blog.axelrobbe.nl/tags/vbond/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SDWAN - Repair a vBond Sync Error</title>
      <link>https://blog.axelrobbe.nl/post/2021-06-04-sdwan-repair-vbond-sync-error/</link>
      <pubDate>Fri, 04 Jun 2021 10:29:15 +0100</pubDate>
      
      <guid>https://blog.axelrobbe.nl/post/2021-06-04-sdwan-repair-vbond-sync-error/</guid>
      <description>Another short entry to help those out who might run into a similar situation as I did this week. In the SD-WAN fabric, every once in a while the controller certificates need to be updated so that the cEdges and vEdges, but also the controllers themselves can authenticate one another. This week, I reconfigured the vManage to use the Cisco Automated using this CVD from Cisco. The process is relatively straight forward, but it&amp;rsquo;s important to update the cEdges and vEdges with a new root certificate so that they will successfully authenticate with the new Cisco issues certificates.</description>
    </item>
    
  </channel>
</rss>
