| To: | nv-l@lists.us.ibm.com |
|---|---|
| Subject: | Re: [nv-l] Why does NV use oid_to_type file ? |
| From: | James Shanks <jshanks@us.ibm.com> |
| Date: | Thu, 13 May 2004 07:26:21 -0400 |
| Cc: | "The nv-l mailing list" <nv-l@lists.us.ibm.com>, owner-nv-l@lists.us.ibm.com |
| Delivery-date: | Thu, 13 May 2004 12:43:09 +0100 |
| Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
| Reply-to: | nv-l@lists.us.ibm.com |
| Sender: | owner-nv-l@lists.us.ibm.com |
| Sensitivity: |
|
Take another look at the oid_to_type file. It contains more than OIDs, which is what snmpwalk will give you. It tells NetView how to draw the object that has that OID |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [nv-l] Why does NV use oid_to_type file ?, Alaa Farrag |
|---|---|
| Next by Date: | RE: [nv-l] Down - Up monitoring ?, Qureshi, Fawad |
| Previous by Thread: | [nv-l] Why does NV use oid_to_type file ?, Alaa Farrag |
| Next by Thread: | Re: [nv-l] Disabling port 162 use, Johanna Hislop |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web