In my experience, the 5.1.1 patch cleared up a bunch of problems
with incorrect status in Collections. There have been a couple of times
lately where I thought I saw something with incorrect status in a collection,
but was unable to recreate it. Usually it happened if the box was under
stress, so I chalked it up to nvcold or nvcollmap being behind, and
being impatient, used Ack/Unack to get it to pick up the current status.
But I am only at the customer site for a week or two, and may not see
things that crop up later.
Are you sure that the thing in the collection and the thing in the IP map
are the same object? (ie they have the same object id, you select one
and both get selected?
Does it look like the node placed in the Collection came from one of
the network submaps rather than from the IP Internet submap? I mean,
you can get a red router with red and green interface cards under it,
and status source is symbol rather than a yellow router with status source
of compound? I think this used to happen a long time ago but I have not
seen it lately.
There also used to be some confusion between the node and its interface,
depending on whether it was discovered by address or by name. Deleting
the node and discovering it by name cleared that up, I think.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
I've encountered a problem twice now with NV 5.1.1 and how it represents
the status of objects and propagates the status within Collections.
Basically, it does not jive with what is in the database or the IP Maps.
I opened a PMR about a month ago, but I seemed to be spending a lot of
time just convincing support that it was a problem. They claimed that
no other customers have reported this. I can't believe this is true.
Is anyone else seeing this?
It seemed to affect multiple objects across multiple collections.
Having performed multiple traces for support, we have yet to find
anything significant.
Thanks in advance
chris.cowan.vcf
Description: Binary data
|