disabling link down/status syslog messages

[Ben Dehner]

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

MII Link Status not OK -- Switch connection at AUI 0/0/0/0
Reset Looper Timeout: DMA timeout ocurrint at 0/0/0/0
...

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?

Thanks

[Steven E. Protter]

Comment out the references to this lan card in /etc/rc.config.d/netconf

Make sure there is no network configuration that references that network. Unplug the network cable and the messages should stop.

SEP

[Joshua Scott]

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.

-Josh

[Ben Dehner]

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.

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.

[Dave Hutton]

From what I've seen you really have to remove any referance to that nic out of the /etc/rc.config.d/netconf file.

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.

I don't think you can just fill it with 0's.

Dave

[Ben Dehner]

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.

[Jeff Schussele]

Hi Ben,

Was this I/F ever used by MC/SG?
Would need to gen a new binary w/o this I/F in the ascii file if so.

And check to see if there are any routes set up through that I/F.
Do netstat -in & netstat -rn come back completely clean of this I/F?

I've never come across a situation where a down, an unplumb & removal from netconf didn't do the job. I don't think you should have to remove a driver to stop this.

Rgds,
Jeff

[Ben Dehner]

No routes, no MC/SG.

For the time being I shut it up by plugging it back in.