Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Interface incorrectly reported as down

Hi All!

We are running Orion Network Performance Monitor Ver. 7.7. We have a couple of machines running SuSE Linux 8.0 with net-snmp 5.2.1. On these machines the eth0 network interface is showing as being "down". As this is the only interface on the machine (other than lo0) and we can read other values via SNMP, it does not make sense that this interface is being reported as down. Further Orion is showing reasonable reponse times and no packet loss. So why are these interfaces being reported as down?

Any help is greatly appreaciated.

Regards,

Jim Mohr

Find more posts tagged with

Accepted answers

All comments

Isaac

Hi Jim,

I would use a MIB browser (SW makes a good one) to check the status of the interface via SNMP.

You are looking for OID: 1.3.6.1.2.1.2.2.1.8

This is the operational status of the interface. If this does not show up(1) then you have a problem.

I hope this helps.

Be fantastic.

jimmo

I have done snmpwalks/snmnpgets on the MIB branches. These interfaces always have an operation status of "down", while they always have and administrative status of "up". In the meantime, found other machines that have the problems. Some of the machines are Solaris 7, Solaris 8 (1 machine) and Suse Linux 8, kernel 2.4.18. This problem does not occur on every machine with the particular version, nor does there seem to be any pattern in terms of specific network cards, just these. Therefore, I am having trouble believing it is a problem with the version of either the operating system or net-snmp.

btp

We experience the very same issue with our DSLAMs from Allied Telesyn. While running on a slight elderly sw release, they have concluded that there's an error in the SNMP support in the DSLAM - thus, upgrading to a later release solves the issue.

Don't know how this would be of any help though...

--
Bjørn Tore