Perhaps the Bay does not make as much noise as the Ciscos. Ping it.
I do not believe netmon -y actively forces discovery the way a stop and
start of netmon does. If the device is heard from, it will be added because
the revisited seedfile allows it; if it is not heard from, it will not be
added.
At restart, all entries are checked, forcing discovery. But generally there
is no difference between discovering Bays and discovering anything else.
Well.... sometimes it has trouble connecting those circuitless IPs!
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Gebhart, Tom (CC-ETS Tools Services)" <Tom.Gebhart@conagrafoods.com>
@tkg.com on 07/03/2001 05:31:06 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc:
Subject: RE: [NV-L] Discovering BayNetworks router in NetView 5.1.3
1. This router is not in DNS. But we have a few other (Cisco) routers
that are not in DNS but are discovered just fine. Only difference is the
label is the ip address and not the hostname.
2. I have tried both the wan interface (the interface closest to the
Netview host) and the ethernet adress, both to no avail.
3. We don't need to use the loopback address. We just usually use
loopback because it is a virtual address that is always up if the router is
up.
Thanks so far, but keep talking to me, Tom G.
-----Original Message-----
From: Scott Barr [mailto:scott_barr@csgsystems.com]
Sent: Monday, July 02, 2001 4:24 PM
To: IBM NetView Discussion
Subject: RE: [NV-L] Discovering BayNetworks router in NetView 5.1.3
This may be a silly question - but is the router resolvable in DNS in both
directions?
Also, is the interface that is listed in DNS the interface "closest" to the
Tivoli box?
By the way - tell Alan Sebastian I said "hello"
Scott Barr - CSG
-----Original Message-----
From: owner-nv-l@tkg.com [mailto:owner-nv-l@tkg.com]On Behalf Of
Gebhart, Tom (CC-ETS Tools Services)
Sent: Monday, July 02, 2001 4:10 PM
To: nv-l@tkg.com
Subject: [NV-L] Discovering BayNetworks router in NetView 5.1.3
AIX 4.3.2, Framework 3.6.2, Netview 5.1.3
I am trying to discover my first BayNetworks router in NetView. We
have a couple hundred Cisco routers and switches in the system already.
Cisco devices get discovered like clockwork after being entered into the
seedfile and issuing a "netmon -y" command. I have entered the ethernet
address of the bay router into our seedfile. Apparently the bay does not
have a loopback address which is what we usually use for discovery.
The router support guys have added our NetView host address and RO
snmp community string to the bay router. We tried letting bay default to
port 162 and we also tried changing the port to 161. No discovery yet. I
can ping the bay from my PC desktop and from the NetView command line. I
can use the MIB browser from the NetView GUI and get system info, interface
info, etc. What am I missing.
Thanks to all for your help. I've had success here before, so I'm
back to the well.
Tom Gebhart
ConAgra Foods
Senior Systems Administrator
(402) 577-3677
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|