Hmmm... Something is very odd. On the basis of what you are saying now, and
what you said earlier, it seems that you may have a problem with name
resolution for
this router.
Try doing this:
host 172.29.21.11
The using the hostname returned from that, do:
host <insert hostname returned here>
Now, if the IP address returned doesn't match 172.29.21.11, this could be
causing the problem.
What do you get? Do the names and addresses match from both tries?
alexis.henry@bnpparibas.com wrote:
> Hi Ray!
>
> Thank you for your advise, the matter is that if i run ovtopodump i cant find
> the router.
> The differents routers are only in object database and not in my topology
> database so i believe i have no need to run ovtopix -U.
>
> Moreover i can ping those deleted routers and i can dump the mib with
> snmpwalk;
> and if i run netmon -M 2 to see ICMP responses i can see that netmon can ping
> thos devices. The strange thong is that the row in netmon.trace is
>
> receiving ping from172.29.21.11 ( )
>
> usually when netmon ping a device we can see the name (or the IP adress) and
> this is not the case here.
>
> Netview 5.1.1 for Aix
> Aix 4.3.3
>
> Regards.
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> alexis.henry@bnpparibas.com wrote:
>
> > Hi list,
> > i have a problem with IBM 3745 router.
> >
> > This central router is connected to many routers. It has 6 interfaces and
> > each
> > interface owns a name in the DNS
> > The loopback adress is set to 127.0.0.1
>
> I see by the outpout of ovobjprint that this device is not in any map (no
> fields
> for Maps Managed and some others). You should consider running ovtopofix -U.
> This
> will force all objects in the database to be placed into all maps. Use with
> caution if you've done customization that required you to delete lots of
> objects
> from one
> of your maps because this will all have to be redone (if you don't have more
> than one map, you don't have to worry about that).
>
> As to how it got that way in the first place - I don't know. Be sure that you
> can forward and reverse resolve the IP name nnt36.
>
> You didn't say what version of NetView you are running. There were some
> defects
> that affected the object from being added properly by netmon in version 5.1
> and
> earlier. I'll bet they are fixed in 5.1.3.
>
> --
> Ray Schafer | schafer@tkg.com
> The Kernel Group | Distributed Systems Management
> http://www.tkg.com
>
> _____________________________________________________________________________________________________________________________________
>
> L integrite de ce message n'etant pas assuree sur Internet, les societes du
> groupe BNP Paribas ne peuvent etre tenues responsables de son contenu.
> Si vous n'etes pas destinataire de ce message, merci de le detruire et
> d'avertir l'expediteur.
>
> ----------------------------------------------------------------------------------
> The integrity of this message cannot be guaranteed on the Internet, companies
> of the BNP Paribas group can not therefore be considered responsible for the
> contents.
> If you are not the intended recipient of this message, then please delete it
> and notify the sender.
> _____________________________________________________________________________________________________________________________________
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
--
Ray Schafer | schafer@tkg.com
The Kernel Group | Distributed Systems Management
http://www.tkg.com
|