RE: [nv-l] Deleted Networks

[Gareth Holl <gholl@us.ibm.com>]

The information that Oliver provided is exactly right. You may be noticing different behaviour from an earlier version because this was changed as version 6.0 (I believe). You are probably only seeing the behaviour for a certain type of device.

In the case of secondary interface support, you can configure groups of devices (based on OID) so that netmon will only treat a device as having secondary addresses if it finds them in the ip.ipAddrTable for that device. This is the "S" flag in the "oid_to_type" file. Refer to the header section of the oid_to_type file for a complete explanation of this flag.

So basically if you remove the S flag from the OID of the device type where you want interfaces to be automatically deleted, this may then allow those interfaces to be removed during the next Daily Config check (assuming they aren't HRSP). However if these devices don't report secondary interfaces correctly via the appropriate snmp variables, then you will end up with interfaces added and deleted continuously without the "S" flag in the oid_to_type file for that particular OID

There is a "T" flag in the "oid_to_type" file also. This is for identifying OID groups as being terminal servers. You may want to play with that also if your devices are terminal servers and see what affect that has on automatic deletion of interfaces that have been removed from the device.

Changes to the oid_to_type file require netmon to be recycled.

If all else fails, delete and re-discover the device. I hope this helps in some way.

Gareth Holl
Staff Software Engineer
gholl@us.ibm.com

IBM Software Group - Tivoli Brand
Research Triangle Park,  North Carolina.

"Francois Le Hir" <flehir@ca.ibm.com> 12/09/2002 12:59 PM

To:        nv-l@lists.tivoli.com         cc:                 Subject:        RE: [nv-l] Deleted Networks

Does it seams to you that it is working the way it should be ?
the daily configuration polling or nmdemandpoll used to do the cleaning of
all the interfaces that don't exist anymore and it is not doing it now. We
end up will lots of "Unmanaged" interfaces in the nodes and some white
subnets on the map that should not be there.
Theses object once unmanaged will never be deleted by Netview. It is not
only useless to have theses objects in Netview but it is also confusing for
the users as it make them believe that the interfaces (and the subnets) are
still there.

nmdemandpoll read the interface table and also look for secondary
interfaces. It should be able to see the change and fix it in the object in
Netview.

Salutations, / Regards,

Francois Le Hir
Network Projects & Consulting Services
IBM Global Services
Phone: (514) 205 6695

Date: Mon, 9 Dec 2002 12:49:47 +0100
To: nv-l@lists.tivoli.com
From: "Oliver Bruchhaeuser" <oliver.bruchhaeuser@de.ibm.com>
Subject: RE: [nv-l] Deleted Networks
Message-ID: <OF694DF1BA.A3432728-ONC1256C8A.004040FB@de.ibm.com>

This is working as designed.

netmon will not delete interface from nodes with either have
secondary interfaces, HSRP interfaces or are "Terminal Servers".
It may accidently delete those types of interfaces or the
interface(es) of the "Terminal Server"

See also Solution 1063700.

Kind regards

Oliver Bruchhaeuser
Tivoli NetView EMEA L2 Support

IBM Deutschland GmbH - ITS Tivoli - Dept. 7977 - Hechtsheimer Str. 2 -
55131 Mainz - Germany
Phone: +49-6131-84-5108 - Fax: +49-6131-84-6585 - email:
bruchhae@de.ibm.com

The Ask Tivoli tool has been replaced by:
  http://www-3.ibm.com/software/sysmgmt/products/support/
AskTivoli to IBM.com search differences:
  https://www.tivoli.com/secure/asktivoli/cgi-bin/diff.html
Howto register:
  http://www-120.ibm.com/software/support/ecare/login?action="">
Help on register:
  http://www-120.ibm.com/software/feedback.jsp?topic=ireg

|---------+---------------------------->
|         |           Leslie           |
|         |           Clark/Southfield/|
|         |           IBM@IBMUS        |
|         |                            |
|         |           30.11.2002 20:07 |
|         |                            |
|---------+---------------------------->
  >
-------------------------------------------------------------------------------------------------|

  |
|
  |       To:       nv-l@lists.tivoli.com
|
  |       cc:
|
  |       Subject:  RE: [nv-l] Deleted Networks
|
  |
|
  |
|
  >
-------------------------------------------------------------------------------------------------|


I used to  believe, in earlier versions, that it  would delete interface
cards for interfaces that were no longer configured. I first noticed it no
longer did
this in 7.1.1. I thought maybe I only imagined that it ever worked that
way.  It
appears that it is now necessary to manually delete those interfaces. I
would suspect that it might be a side-effect of all the code changes
required to support of RFI. Have you noticed whether they fall under the
'node down
delete interval'? I have not checked. I just make it a policy to manually
delete them when the Change Control notification (smile) tells me that
an interface has been deconfigured.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit

                      "Barr, Scott"
                      <Scott_Barr@csgsy        To:
                      <nv-l@lists.tivoli.com>
                      stems.com>               cc:
                                               Subject:  RE: [nv-l] Deleted
                      Networks
                      11/27/2002 01:52
                      PM

I have observed this phenomena using v7.1.3 under Solaris 2.8. The device
in question is a Cisco 6509 switch and the subnets were VLANs that were
removed. Demand poll seemed to have no effect on these "unreachable"
subnets. I have been suspicious of it but had not come to any conclusion. I
think there is something there, just can't put my finger on it.

> -----Original Message-----
> From: Mike Walsh [mailto:Mike.Walsh@us.ing.com]
> Sent: Wednesday, November 27, 2002 12:16 PM
> To: nv-l@lists.tivoli.com
> Subject: [nv-l] Deleted Networks
>
>
> Greetings to you all,
>
> I have encountered an interesting phenominum with 7.1.3
> running on a sun
> machine with the Magnum Switch Coordinator. I am hoping
> someone could steer
> me straight on this.
>
>  We have a Checkpoint device at a remote site which had a
> x.x.x.x network
> on it that had been deleted several weeks ago.  I noticed
> that OLD network
> was still being displayed ( I had set it to unmanaged while
> confirming that
> it had actually been deleted)   I ran a demand poll on the checkpoint
> device and saw that this network was still defined.  After
> double checking,
> I confirmed that it no longer existed and proceeded to delete
> the network
> from all NV displays.  After running another demand poll I
> saw that it had
> disappeared from the poll results.
>
> My question is - am I misinterpreting the function of a
> demand poll?  I
> always thought it to actually check devices for interfaces and their
> status) or do we have a problem with 7.1.3?
>
> Any guidance on this is very greatly appreciated.
>
> Mike
>
>
> Mike Walsh
> ****Please Note - New EMAIL Address  mike.walsh@us.ing.com*********
> 612-342-3118




---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)