<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: disabling link down/status syslog messages in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145129#M572308</link>
    <description>if you don't need the network interface any longer, then just diable it.  the simplest way is to use SAM.  just disable the appropriate interface in the networking section.&lt;BR /&gt;&lt;BR /&gt;-Josh</description>
    <pubDate>Mon, 15 Dec 2003 14:20:16 GMT</pubDate>
    <dc:creator>Joshua Scott</dc:creator>
    <dc:date>2003-12-15T14:20:16Z</dc:date>
    <item>
      <title>disabling link down/status syslog messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145127#M572306</link>
      <description>I have a NIC (10/100) interface in my HPUX 11.0 server which I have disconnected from the network.  I am now getting a lot of syslog messages of the form&lt;BR /&gt;&lt;BR /&gt;MII Link Status not OK -- Switch connection at AUI 0/0/0/0&lt;BR /&gt;Reset Looper Timeout: DMA timeout ocurrint at 0/0/0/0&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;I know what the problem is -- I disconnected the interface.  I don't need it connected any more.  How do I disable whatever monitoring daemon is spawing these error messages?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Dec 2003 14:11:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145127#M572306</guid>
      <dc:creator>Ben Dehner</dc:creator>
      <dc:date>2003-12-15T14:11:35Z</dc:date>
    </item>
    <item>
      <title>Re: disabling link down/status syslog messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145128#M572307</link>
      <description>Comment out the references to this lan card in /etc/rc.config.d/netconf&lt;BR /&gt;&lt;BR /&gt;Make sure there is no network configuration that references that network.  Unplug the network cable and the messages should stop.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 15 Dec 2003 14:19:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145128#M572307</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-12-15T14:19:44Z</dc:date>
    </item>
    <item>
      <title>Re: disabling link down/status syslog messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145129#M572308</link>
      <description>if you don't need the network interface any longer, then just diable it.  the simplest way is to use SAM.  just disable the appropriate interface in the networking section.&lt;BR /&gt;&lt;BR /&gt;-Josh</description>
      <pubDate>Mon, 15 Dec 2003 14:20:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145129#M572308</guid>
      <dc:creator>Joshua Scott</dc:creator>
      <dc:date>2003-12-15T14:20:16Z</dc:date>
    </item>
    <item>
      <title>Re: disabling link down/status syslog messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145130#M572309</link>
      <description>I have already used ifconfig to set the interface to 'down' and IP address 0.0.0.0.  I have also made these changes to /etc/rc.config.d/netconf.  I've even tried "unplumb"ing the interface.&lt;BR /&gt;&lt;BR /&gt;Since the unplugged cable and link loss is a hardware fault, I think STM is generating these messages, because it believes that this device needs to be monitored.</description>
      <pubDate>Mon, 15 Dec 2003 14:38:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145130#M572309</guid>
      <dc:creator>Ben Dehner</dc:creator>
      <dc:date>2003-12-15T14:38:09Z</dc:date>
    </item>
    <item>
      <title>Re: disabling link down/status syslog messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145131#M572310</link>
      <description>From what I've seen you really have to remove any referance to that nic out of the /etc/rc.config.d/netconf file.&lt;BR /&gt;&lt;BR /&gt;I've even used same to remove an interface, rebooted.  And it still trys to do stuff with it.  It wasn't until I removed all the info to that card did it ingore it.&lt;BR /&gt;&lt;BR /&gt;I don't think you can just fill it with 0's.&lt;BR /&gt;&lt;BR /&gt;Dave&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Dec 2003 14:41:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145131#M572310</guid>
      <dc:creator>Dave Hutton</dc:creator>
      <dc:date>2003-12-15T14:41:53Z</dc:date>
    </item>
    <item>
      <title>Re: disabling link down/status syslog messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145132#M572311</link>
      <description>I think I found what's generating error.  It is coming from the btlan3 driver bound to this interface in the kernel.  (This is the core 10/100 interface.)  I'm guessing that I may need to reboot the system and/or apply the latest patch to shut it up.  I've tried removing the device with rmsf -H, but it doesn't work, and since the driver is static, I can't remove it from the kernel without a reboot.  But since the error is coming from a hardware driver, changing an init file isn't going to stop the error message.</description>
      <pubDate>Mon, 15 Dec 2003 16:39:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145132#M572311</guid>
      <dc:creator>Ben Dehner</dc:creator>
      <dc:date>2003-12-15T16:39:43Z</dc:date>
    </item>
    <item>
      <title>Re: disabling link down/status syslog messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145133#M572312</link>
      <description>Hi Ben,&lt;BR /&gt;&lt;BR /&gt;Was this I/F ever used by MC/SG?&lt;BR /&gt;Would need to gen a new binary w/o this I/F in the ascii file if so.&lt;BR /&gt;&lt;BR /&gt;And check to see if there are any routes set up through that I/F.&lt;BR /&gt;Do netstat -in &amp;amp; netstat -rn come back completely clean of this I/F?&lt;BR /&gt;&lt;BR /&gt;I've never come across a situation where a down, an unplumb &amp;amp; removal from netconf  didn't do the job. I don't think you should have to remove a driver to stop this.&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;Jeff</description>
      <pubDate>Mon, 15 Dec 2003 16:50:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145133#M572312</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2003-12-15T16:50:51Z</dc:date>
    </item>
    <item>
      <title>Re: disabling link down/status syslog messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145134#M572313</link>
      <description>No routes, no MC/SG.&lt;BR /&gt;&lt;BR /&gt;For the time being I shut it up by plugging it back in.</description>
      <pubDate>Mon, 15 Dec 2003 17:11:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disabling-link-down-status-syslog-messages/m-p/3145134#M572313</guid>
      <dc:creator>Ben Dehner</dc:creator>
      <dc:date>2003-12-15T17:11:33Z</dc:date>
    </item>
  </channel>
</rss>

