[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

3250.0. "Find address...........help!" by OPCO::NET_PJD () Thu Feb 08 1996 02:02

Hubwatch for Unix V4.1.1, MAM version V4.1.0.

Hi all,

I'm using the Find Address utility under Hubwatch and I'm having problems.

When searching using an IP address which I know is configured on a system
connected to the hub I get:-

"Unable to resolve network to physical Address, Search aborted"

The system in question is connected to a UTP port (port 4) on a Decswitch900EF 
in slot 3. (It is logically connected to the thinwire via port 3)

Looking at the window that I fired Hubwatch up from I can see the ping as 
being successful.  Surely if the ping is successful, the echo reply has 
come back and this should contain the physical address of the relevant 
system.  Am I missing something?

Also, if it works, should it tell me which port the address is seen on, 
ie "Slot 3, port 4"

Any help, hints pointers etc greatly appreciated.

Cheers,

Phil.
T.RTitleUserPersonal
Name		DateLines
3250.1NETCAD::MILLBRANDTanswer mamThu Feb 08 1996 10:1114
I'm not a HUBwatch person, but...

SNMP repeaters (and our proxied repeaters) implement the repeater mib
which contains a database of MAC addresses.

Your station is coming in on a DECswitch.  While switches maintain
a forwarding database in high speed cache, it is not a mib object.
I suspect HUBwatch has no way to access this info.

Looking at the HUBwatch Help for Find Address, the first sentence
says, "Searches for Ethernet stations connected to ports of
90-series and 900-series repeaters."

	Dotsie
3250.2NPSS::WADENetwork Systems SupportThu Feb 08 1996 10:4324
   >      
   > Looking at the HUBwatch Help for Find Address, the first sentence
   > says, "Searches for Ethernet stations connected to ports of
   > 90-series and 900-series repeaters."
   >      
   
    I totally agree that this is the way it is and looking in help would
    have answered the question but
          
   > Your station is coming in on a DECswitch.  While switches maintain
   > a forwarding database in high speed cache, it is not a mib object.
   > I suspect HUBwatch has no way to access this info.
   >      
                                  
    From RFC1493 Bridge MIB
    
      Dot1dTpFdbEntry ::=
                      dot1dTpFdbAddress
                      dot1dTpFdbPort
                      dot1dTpFdbStatus
             
    Bill
3250.3Not Rocket Science, just not high P.SLINK::HOODThey call me MISTER Dilbert.Thu Feb 08 1996 11:2515
    Dotsie is right and Bill is right.
    
    HUBwatch's Find Address function only works on repeater ports. From
    time-to-time we've talked about changing it so it looks on bridge
    ports, too.  But it's never been a high enough priority.
    
    As Bill pointed out, it's not rocket science to make this happen.
    
    
    If this is a problem for your customer, the best thing to do would
    be to drop a line to our beloved Product Manager, Jack NAC::Forrest.
    
    
    Tom Hood
    clearVISN Apps
3250.4Thanks.......OPCO::NET_PJDThu Feb 08 1996 16:435
    Thanks for your prompt replies.......
    
    Cheers,
    
    Phil.