In general, if a device's characteristics are not being reported
correctly, especially is you are using an enterprise specific
application (Nways, Optivity, Transcend, etc) a good possible
cause is the agent code/operating code on the device itself.
Check with support for the device or the software and find
out if there are patches for the version of the hardware code
you're using or if support recommends an upgrade.
And make sure your ovsnmp isn't tripping you up. For example, if
the R/O community is OK, but some wild card or global default R/W
community conflicts with the device, or if you have a R/W community
defined but the device does not have a R/W community set, it can
cause incomplete or incorrect polling from some applications.
I suggest these things because I haven't had problems at customers
with 8275's. Any chance you've done incorrect cut/paste? That can
cause confusion, too.
Hope it helps.
Leslie Clark wrote:
>
> This may be a clue for you --
> at a recent customer site I had some 8275's ( IBM fastethernet desktop
> switches) show up with isCard set to true. Not all of them, just some.
> Nways 1.2.3 was on. Rediscovery, ovtopofix did not help, and
> usually the ovtopofix helps since it does all of that setting if isNode.
> I just ran an nvdbimport and set them all to isCard is false. I won't
> be back there for a couple of weeks, and will need to investigate
> further then. More should have been installed by then, too.
> I had AIX 4.2.1, Netview 5.1.2, Nways 1.2.3
>
> Interesting....
>
> Cordially,
>
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
>
> Hello,
>
> Here is a problem about which I called Support several weeks ago. It doesn't
> seem obvious, but perhaps someone already got through it.
>
> NV 5.1.1 on AIX 4.2.1 + NWays 1.2.1 + Ciscoworks 4.0.
>
> When discovered by NetView, most (but not all) of our routers are stored into
> object DB with an abnormal field: 60 - isInterface, which value is set to
> TRUE.
> First consequences: the IPMap description (Edit/Description) is empty (i.e. it
> provides the mask you use when adding a new node) and Ciscoworks is unable to
> get routers' community names (don't ask me why).
> It seems that NWays is involved in that affair (a router is well recorded when
> you stop cmld and nvot-server just before discovery), but lab said it was not
> the culprit.
>
> Did anyone encounter such a problem?
> Any help appreciated.
> Thanks.
> Bernard Envain - CIC Banque Scalbert-Dupont
> 03 20 12 60 47 - Fx.: 03 20 12 60 80
>
> ------------------------------------------------------------------------
> Name: att1.htm
> att1.htm Type: Hypertext Markup Language (text/html)
> Encoding: base64
> Description: Internet HTML
|