[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

1107.0. "Telnet session address not shown from hubwatch" by KERNEL::WARDJO () Mon Jun 13 1994 07:56

    Hello,
    
    I have a customer who is running Hubwatch V2.0 for VMS with a Dechub90 and
    decagent 90 V1.1.
    
    He creates telnet sessions from Decserver 90M and then looks at these
    from hubwatch "Terminal server summary window" & from "Terminal server
    session detail window". He has noticed that some of the sessions show
    up with an address of ?.?.?.? instead of the actual telnet address
    used.
    
    Can anyone explain under what circumstances you would see an address
    represented like this? - I have been unable to reproduce the symptoms
    with a decserver 90TL running the same version of NAS software.
    
    
    Thanks in advance,
    
    Jon
T.RTitleUserPersonal
Name		DateLines
1107.1KALI::IACOBONETue Jun 14 1994 19:167
    The question marks are displayed when the server can't identify the
    remote end of the connection. I'd like to know what the customer is
    connecting the 90M to. I'll try to re-create it here.
    
    Dave Iacobone
    HUBwatch development team
1107.2Connecting to Vax with UCXKERNEL::WARDJOWed Jun 15 1994 07:1018
    Dave,
    
    Thanks for the reply, - The Decserver 90M is in a Dechub 90. Also in
    the hub is a Wanrouter 90 - the connection is made accross this 64k
    link to a DECnis and on to a Vax running UCX.
    
    The NMS is on the same lan as the Vax the customer is connecting to.
    
    DS90M address - 93.57.227.203 Mask 255.255.255.0
    Vax running ucx address 93.57.4.101
    
    Do you require further information?
    
    Thanks & regards,
    
    Jon
1107.3SLINK::HOODI'd rather be at the KennebecWed Jun 15 1994 11:047
Something that may be helpful is the server's
	> SHOW PORT [nn | ALL] SESSIONS
command.  If the address shows up there, there may be a problem somewhere
in SNMP.  Otherwise, the server cannot identify the remote node.

Tom Hood
HUBwatch
1107.4THE ADDRESSES SHOW ON THE SERVERKERNEL::WARDJOFri Jul 01 1994 06:1812
    Tom,
    
    I finally got the customer to do the SHOW PORT [nn | ALL] SESSIONS
    command. All the addresses show up on the server.
    
    Have you been able to reproduce this problem?
    
    
    Regards,
    
    Jon