Rob Napholz wrote:
> What I seeing is multiple node up events without any node or interface
> down events.
> So how/why is netview sending a event if the status is not changing
MLM's send status events when they are restarted. Can you send me a sample of
up events ytou are seeing?
Netmon looks for these traps and updates status (if required). Normally these
traps are not logged. You can go into xnmtrap, select the Enterprise for the
trap, and then look at the specific trap. See if the trap is set to log only,
don't log. It can be changed to don't log. Netmon will still see the trap and
the right thing.
> Ps I have opened a pmr
> James Shanks wrote:
> > Just a couple of things - I don't know if they will help -- and if not,
> > you
> > may want to take the issue up with Support so that someone can separate the
> > important facts from the rest. If you are truly having a problem, you will
> > have
> > to investigate it one interface and node at a time.
> > First, you must distinguish between Node Up/ Node Down events and Interface
> > Up/
> > Interface Down events. These are not the same and will not be issued under
> > the
> > same conditions. Interfaces will be Up or Down depending on whether they
> > respond to pings, but Nodes will be Up or Down depending on the status of
> > all
> > their interfaces. So if you have a node with more than one interface, and a
> > particular one goes down, but the others remain up, you get an Interface
> > Down
> > event for that interface but a Node Marginal, not a Node Down event, for the
> > node. The Interface Down/Node Down, Interface Up/Node Up is only synonymous
> > when
> > there is only one interface on the box. So there first thing is to make
> > sure
> > you are looking at the right set of events.
> > Second, NetView basically sends an event every time a status in the database
> > changes. He does not discard any. You could build a ruleset to do that,
> > but
> > that is not a default function for the product.
> > James Shanks
> > Tivoli (NetView for UNIX) L3 Support
> > Rob Napholz <tel1rxn AT njcmail.ups DOT com> on 08/25/99 10:20:09 AM
> > Please respond to tel1rxn AT njcmail.ups DOT com
> > To: NV-L AT UCSBVM.UCSB DOT EDU
> > cc: (bcc: James Shanks/Tivoli Systems)
> > Subject: multiple netview mlm up traps
> > Hello
> > On Aug 1 router "X" went down i received a down event, 3 hrs later when
> > the router
> > came up I received a up event. On Aug 2,3,4,6 I also received up events,
> > no downs.
> > On Aug 9 router "X" went down again, i received a down and a up event
> > On Aug 14,14,16,17,19,20,23,24 I also received up events, no downs.
> > This is just a example of 1 router. The problem is wide spread.
> > The router/interface only went down twice down. Why am I getting all of
> > these up events ?
> > The up events are for every interface on the router. The down event is
> > for only one interface.
> > The traps are all netview traps from a AIX MLM.
> > Should netview be discarding all of these traps since the are no
> > corresponding
> > down traps ?
> > why is netview generating all of these traps ?
> > If the problem was a missed poll/ping one would expect to see down
> > events not up.
> > Any ideas
> > thanks Rob
Ray Schafer | schafer AT tkg DOT com
The Kernel Group | Distributed Systems Management