Heh, falls under the category of BEEN THERE and DONE THAT.
Glad to help.
-----Original Message-----
From: Scott Bursik [mailto:tivoliesm@hotmail.com]
Sent: Thursday, October 18, 2001 1:45 PM
To: nv-l@tkg.com
Subject: RE: [NV-L] Interface name/ip status Changing?
Let me start by saying YOUR RIGHT!
Here is what I found:
13:09:10 WARNING: There was a duplicate IP address 10.10.10.2 on
pbsxd200004.pepsi.com and pbsxd200010.pepsi.com.
13:09:11 WARNING: There was a duplicate IP address 10.10.10.130 on
pbsxd200004.pepsi.com and pbsxd200010.pepsi.com.
Thanks,
Scott
>From: "Barr, Scott" <Scott_Barr@csgsystems.com>
>Reply-To: IBM NetView Discussion <nv-l@tkg.com>
>To: "'IBM NetView Discussion'" <nv-l@tkg.com>
>Subject: RE: [NV-L] Interface name/ip status Changing?
>Date: Thu, 18 Oct 2001 13:33:59 -0500
>
>The reason this usually happens is because there are duplicate IP addresses
>on the non-routable networks. For instance, if you have an SP2 complex,
>some
>of the switch interfaces (internal) participate in a 1.1.1 or 2.2.2
>network.
>If some other box in the network has a secondary interface with the same
>address (again - a subnet not reachable by netview or else the machine
>would
>report duplicate IP as soon as it was put on the network).
>
>The only solution I know of is to re-ip the offender.
>
>-----Original Message-----
>From: Scott Bursik [mailto:tivoliesm@hotmail.com]
>Sent: Thursday, October 18, 2001 1:29 PM
>To: nv-l@tkg.com
>Subject: RE: [NV-L] Interface name/ip status Changing?
>
>
>
>The issue is, he will change back and forth throughout the day. The name
>cahnges back to the original en3 name from the longer name. Its like it is
>rediscivering the node several times a day with different interface names.
>If I unmanage one of the non-pingable interfaces (we will call it en3)
>later
>
>in the day it will become managed again and the name will be the en3;
>Product: PCI Ethernet Adapter........ So NetView thinks its a new interface
>and adds it and removes the other interface. Then later on it doesit again,
>naming the interface back to en3 adn thus creating more interface traps and
>changing the status of the node back to marginal. Hope this makes sense.
>
>Scott
>
>
> >From: "Barr, Scott" <Scott_Barr@csgsystems.com>
> >Reply-To: IBM NetView Discussion <nv-l@tkg.com>
> >To: "'IBM NetView Discussion'" <nv-l@tkg.com>
> >Subject: RE: [NV-L] Interface name/ip status Changing?
> >Date: Thu, 18 Oct 2001 12:56:02 -0500
> >
> >
> >1003176713 1 Mon Oct 15 15:11:53 2001 pbsxd200009stby.pepsi.com N
> >Interface
> >
> >css0 Added
> >
> >===> Discovery adds it
> >
> >1003176713 1 Mon Oct 15 15:11:53 2001 pbsxd200009stby.pepsi.com N
> >Interface
> >
> >en0 Added
> >
> >===> Discovery adds it
> >
> >1003176714 3 Mon Oct 15 15:11:54 2001 pbsxd200009stby.pepsi.com N
> >Interface
> >
> >css0 down.
> >
> >===> Unpingable interface - first status poll fails this interface
> >
> >1003176714 7 Mon Oct 15 15:11:54 2001 pbsxd200009stby.pepsi.com N Node
> >marginal.
> >
> >===> Box is now marginal because one or more of its interfaces are down.
> >
> >1003176714 3 Mon Oct 15 15:11:54 2001 pbsxd200009stby.pepsi.com N
> >Interface
> >
> >en0 down.
> >
> >===> Status poll fails to this interface as well - probably non pingable
> >
> >1003177212 7 Mon Oct 15 15:20:12 2001 pbsxd200009stby.pepsi.com n Demand
> >polling on node pbsxd200009stby.pepsi.com.
> >
> >===> User initiates demand poll
> >
> >1003177227 4 Mon Oct 15 15:20:27 2001 pbsxd200009stby.pepsi.com N
> >Interface
> >
> >Descriptor for en3 changed to "en3; Product: PCI Ethernet Adapter
> >(23100020)
> >
> > Manufacturer: not available! Part Number: 091H0397 FRU Number:
>091H0397
> >".
> >
> >===> Demand poll finds the en3 interface (snmp get of interface table I
> >assume)
> >
> >1003177227 4 Mon Oct 15 15:20:27 2001 pbsxd200009stby.pepsi.com N
> >Interface
> >
> >Descriptor for en1 changed to "en1; Product: PCI Ethernet Adapter
> >(23100020)
> >
> >
> >===> Demand poll finds en1 inteface information (snmp get of interface
> >table)
> >
> >1003177227 4 Mon Oct 15 15:20:27 2001 pbsxd200009stby.pepsi.com N
> >Interface
> >
> >Descriptor for en0 changed to "en0; Product: PCI Ethernet Adapter
> >(23100020)
> >
> > Manufacturer: not available! Part Number: not available! FRU Number:
>not
> >available! ".
> >
> >===> again en0 information obtained via the demand poll.
> >
> >I don't see anything wrong here? The only issue may be that the node will
> >be
> >degraded unless you unmanage the non-pingable interfaces OR you must use
> >"$"
> >in the seed file for this box so he uses SNMP status polls. I assume at
> >least some of these interfaces are non-pingable.
> >
> >_________________________________________________________________
> >Get your FREE download of MSN Explorer at
>http://explorer.msn.com/intl.asp
> >
> >_________________________________________________________________________
> >NV-L List information and Archives: http://www.tkg.com/nv-l
> >_________________________________________________________________________
> >NV-L List information and Archives: http://www.tkg.com/nv-l
>
>
>_________________________________________________________________
>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>_________________________________________________________________________
>NV-L List information and Archives: http://www.tkg.com/nv-l
>_________________________________________________________________________
>NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
|