Conference netcad::hub_mgnt

    >    1. The node name in the hot list is in the form DEC -xx-xx-xx for
    >	a MAC address of AA-00-04-xx-xx-xx . Can the node address be changed
    >	to reflect the true node name ?

   
  Yes 
  you can edit a optional file called macaddr.nam. in NSHOME/usr
  if this file is present PRObEwatch use it for mapping MAC address into
  name.

>    2. I have not run V1.0 of Probewatch, but I read from the V1.0 manual
>	about the Discovery function which runs in the background and produced 
>	a data file that maps MAC address with node name . I assume that it 
>	produce real node name . Is this correct ? If so, is there similar 
>	functionality in V3.2 ? If not, what is the reason for dropping such
>	a function ?

  i think , this option worked only with IP , now with the new Firmware
            of the probe, the probe is available to learn all ip address
            directly

  jean-yves

    
    Does it work for Windows ProbeWatch ?
    I've edited a macaddr.nam, but the host list doesn't reflect the node
    name.
    What should be the contents of this file?
    
    thanks in advance
    Jordi Manchon 

   Does it work for Windows ProbeWatch ?
   yes

   What should be the contents of this file?

  # sample macaddr.nam
  #
  abhay-the-arrow       0000c0b75985
  alpine                08005acd834c
  arrow         0000c0b75985
  something     00808c01084f


  jean-yves

GULP!


One has to *EDIT* all the mac addresses into the system.....

surely not!

is there some way to get the probe to autolearn addresses???


thanks
davet

    I will ask Frontier again to automatically calculate the DECnet address
    from the AA-00-04-xx-xx-xx MAC address. Then is there an ASCII file in 
    Pathworks that maps names to DECnet addresses? I haven't been able to 
    find such a file. 
    
    Is there some way in DECnet VMS to dump just address and name info?
    I ask this because I don't think most people keep a big DECnet database
    on their PC or Unix workstation.
    
    With V2.6 probe firmware, you won't  have to put in the MAC to name 
    translations for IP nodes, but you will need IP addresses and names 
    in the hosts file on the Windows version.
    

    
    JAck,
    
    	If you can get them to calculate the DECnet address, I'll write a
    command procedure you can put on the Internet to create the file. This
    is pretty simple with DCL. 
    
    	However, do we have to wait for the translation or will it support
    reading the name of the system from a file now? We could generate a
    file with Ethernet DECnet addresses in the meantime until they
    translate the address to a standard DECnet address. 

    Actually, with V2.6 firmware and PROBEwatch V3.2, if you install the 
    DECnet domain in NET mode, then the Host List will display DECnet
    addresses. However, the Host List in the All domain will still show 
    MAC addresses.
    
    PROBEwatch V3.2 will support MAC address translation to Names if you
    create the MACADDR.NAM file. But isn't it much more difficult to create 
    this file with a script than it would be to create a DECnet address to 
    name file?
    
    jack

	Just an update to this, as I'm searching to resolve a probe problem.

	A few years ago I wrote a VB program that would read a text file
	containing "nodename DECnet_address", created using the NCP SHOW
	KNOWN NODES command (and sorted and edited a bit), and create 
	another text file with "nodename = MAC_address". I used the output
	file as the hostname file for IRIS (DWNODES.INI) so I could see host 
	names instead of DECnet addresses.

	The program is called CONVERT*.EXE on TROOA::[fal$server]. This little
	app will also allow you convert addresses manually in either direction
	between DECnet and MAC (both Ether and Token). A stripped down
	version, that can not use text files, is called CVTADDRS.EXE at the
	same location.

	-Larry