<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Troubleshooting on Network Haven</title>
    <link>/tags/troubleshooting/</link>
    <description>Recent content in Troubleshooting on Network Haven</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 16 May 2026 12:00:00 +0200</lastBuildDate>
    <atom:link href="/tags/troubleshooting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cisco ignore startup configuration</title>
      <link>/posts/2026/cisco-ignore-startup-configuration/</link>
      <pubDate>Sat, 16 May 2026 12:00:00 +0200</pubDate>
      <guid>/posts/2026/cisco-ignore-startup-configuration/</guid>
      <description>&lt;p&gt;The startup configuration can be bypassed by booting into ROMMON or during normal operation. In either case, a reboot is required.&lt;/p&gt;&#xA;&lt;p&gt;This is particularly useful, for example, if you need to perform a password recovery because you have forgotten your password, or for troubleshooting purposes.&lt;/p&gt;&#xA;&lt;h2 id=&#34;configuration-in-ios&#34;&gt;Configuration in IOS&lt;/h2&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;Switch# configure terminal&#xA;! to activate&#xA;Switch(config)# system ignore startup-config&#xA;&#xA;! to deactivate&#xA;Switch(config)# no system ignore startup-config&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;configuration-in-rommon&#34;&gt;Configuration in ROMMON&lt;/h2&gt;&#xA;&lt;p&gt;In the background, the IOS command simply sets the ROMMON variable SWITCH_IGNORE_STARTUP_CONFIG to 1 or 0 which we can also do manually.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Issue detecting domain network on domain controller when using NIC teaming</title>
      <link>/posts/2026/issue-detecting-domain-network-on-domain-controller-when-using-nic-teaming/</link>
      <pubDate>Fri, 10 Apr 2026 23:10:03 +0200</pubDate>
      <guid>/posts/2026/issue-detecting-domain-network-on-domain-controller-when-using-nic-teaming/</guid>
      <description>&lt;p&gt;We had an issue where our domain controller lost its domain network profile after a reboot. When it came back up it was set to public instead of domain.&lt;/p&gt;&#xA;&lt;p&gt;The problem occurred only when Windows NIC teaming (switch-independent) was used in combination with two network adapters in the team. As soon as one network adapter was disabled from the team (while the other remained active), the network profile (domain) was recognized correctly.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
