Conference netcad::hub_mgnt

    
    John,
    
    	Make sure SLIP is enabled for the port. Also, not sure off hand
        if it matters, but you might try the CHANGE INTERNET ADDRESS command 
        to give the server an IP address and mask.
    
    Hope that helps,
    Bob
    
    

    I have now managed to issue all the setup commands - including enabling
    SLIP for the terminal server port.
    
    My configuration is as follows:
    
    +---------+		+--------+		+-----------+
    |VAX host |		| DS90TL |		|Hub 900    |
    +---------+---------+--------+--------------+-----------+
    135.3.30.29		135.3.40.41		135.3.40.34
    
    The DECserver 90TL is housed in a DEChub 900.
    
    I can do a UCX PING to the terminal server but not to the DEChub 900
    OBM port.  The physical cabling checks out OK.
    
    If I connect to the DECserver and issue SHOW PORT ALL, my SLIP port
    shows up as LOCAL with status CONNECTING.
    
    Is there something I have forgotten to do.
    
    Regards,
    
    John
    

    
    John,
    
    	Check that speed settings on SLIP port and OBM port match.
    
    Bob

    Bob,
    
    The speed on the OBM port and SLIP port do match.  I have also tried
    varying the speed but that down not seem to help either.
    
    I have read the DEChub 900 owners manual again and am slightly
    confused.  On page 4-2 it details the setting up of the OBM port.  It
    states that "the IP address and port speed at each end of the
    communications link must be identical."   Is this trying to say that
    the Terminal Server IP address and the OBM IP address should be the
    same?  Or is it just saying that the OBM port should have a unique IP
    address?
    
    Any help appreciated,
    
    John
    

John,


>    I have read the DEChub 900 owners manual again and am slightly
>    confused.  On page 4-2 it details the setting up of the OBM port.  It
>    states that "the IP address and port speed at each end of the
>    communications link must be identical."   Is this trying to say that
>    the Terminal Server IP address and the OBM IP address should be the
>    same?  Or is it just saying that the OBM port should have a unique IP
>    address?

I think you've got the right idea.

It's saying that the out-of-band IP address should match to IP address
of the port which the terminal server is providing SLIP service.
 
You have to give the terminal server an IP address, say a.a.a.a.  You then
give the server's port an ip address, say b.b.b.b.  (This is actually 
telling the terminal server to perform proxy ARP and to provide SLIP
service for the station attached to the port.)  You then have to give 
the hub's out-of-band management port the b.b.b.b address.

						-Shawn     

I have just managed to get an identical configuration working today (pity I
didn't see this note last week!).

You could also try checking SHOW PORT n SLIP CHAR to make sure that the SET PORT
n SLIP HOST b.b.b.b command has not been forgotten by the server (it seems to do
this whenever I LOGOUT PORT n). SHOW PORT n COU and SHOW PORT n SLIP COU will
give you some useful stats. Try pinging for the OBM IP address (b.b.b.b) from an
MSU management station. If all is configured properly you should see an ARP
entry appear for that address with the servers ethernet address. If you do not
see this then the server configuration is wrong. If that is OK look at the
counters to see if the server is sending out any packets on the serial line. (We
ended up putting a VT420 in DIsplay Controls mode in place of the OBM port -
once we got to the stage that we could see characters then everything was
working).

If things still don't work out for you send me mail and I'll send you our
server's complete setup.

Antonio

PS - even when it works pinging for the hub from the DS90TL does *NOT* work -
ping from somewhere else!

    Shawn
    
    Thanks for your help.
    
    The SLIP address on my terminal server port is identical to that on the
    OBM port (so is the baud rate).  If I connect to the terminal server 
    using NCP CONN ... and issue a SHOW PORT ALL command the port connected 
    to the OBM port (the one offering the SLIP service) shows its status as 
    connected.
    
    Also, if I now issue a UCX PING command to the OBM port I can see the
    light on the DS90TL (that is connected to the OBM port) flashing
    (probably indicating that data is trying to get through).  However the
    result for my ping command is...
    
    %UCX-I-LOOPINACT, LOBM06 does not respond
    
    I have included all the characteristics of the terminal server port
    providing the SLIP service...
    
    Port 3:				Server: LS9005
    
    Character Size:	8		Input Speed:		38400
    Flow Control:	None		Output Speed:		38400
    Parity:		None		Signal Control:		Disabled
    Stop Bits:		1	
    
    Access:		Local		Local Switch:		None
    Backward Switch:	None		Name:			PORT_3
    Break:		Disabled	Session Limit:		4
    Forwards Switch:	None		Type:			Ansi
    Default Protocol:	SLIP
    
    Dedicated Service:	SLIP
    
    Authorized Groups:	0
    (Current) Groups:	0
    
    Enabled Characteristics:
    Autoconnect, Autoprompt, Broadcast, Failover, Lock, Loss Notification,
    Message Codes, SLIP, Verification
    
    I know I must be fairly close to getting this working, but I can't
    figure out what I am missing.
    
    Any help appreciated,
    
    John
    

    Antonio,
    
    Thanks for your quick response.
    
    If I do PING to the OBM port I get the response LOBM06 does not
    respond.  If I then do UCX SHOW SRP I see the host LOBM06 and the
    Ethernet address of my DS90TL.  
    
    ALso if I log out the terminal server port and reload the server it
    dows pick up the correct IP address.
    
    If I do SHOW PORT 3 SLIP COUNT while I am trying to PING LOBM06 then
    I can see PORT 3 sending 1700 bytes of data but not receiving any.
    
    It appears to me that the Termianl Server port is configured OK but the
    OBM port is not sending any information.
    
    I will try and connect a VT420 to the OBM port as you have described.
    
    If you could post your terminal server port settings here or
    alternatively mail them to me ARRODS::GILLJ I would appreciate it.
    
    Thanks,
    
    John
    

    
    
    I know earier that you said the cabling checked but just to be sure.
    Are you using the h8571-j adaptor on the OBM port and a bn24h crossover
    cable.
    

    Just a couple of comments.  
    
    You should use DEFINE or CHANGE rather than SET when doing all this;
    SET only modifies the volatile configuration so it will be lost the
    next time the terminal server resets.
    
    The error message in .0 means that the SLIP port address is not in the
    same subnet as the address of the terminal server itself - an illegal
    configuration.  For example, if the terminal servers address is
    16.20.100.5 and the subnet mask (SHOW INTERNET MASK) is 255.255.255.0
    then the port address must be 16.20.100.<something>.
    
    Note that you cannot change the subnet mask when the server has an
    address; you must delete the address (CHANGE INTERNET ADDRESS NONE, I
    think) and then change the mask and then re-configure the address.
    
    If it still isn't working, post the results of:
    
    SHOW SERVER
    SHOW INTERNET
    SHOW PORT <n> 
    SHOW PORT <n> STAT
    SHOW PORT <n> SLIP
    

    RE: .10
    
    Clarifications to your comments:
    
    > SET only modifies the volatile configuration so it will be lost the
    > next time the terminal server resets.
    
    Volatile port characteristics, such as SET PORT x SLIP HOST ADDRESS,
    are lost each time the port is logged out.  It does not require a reset
    of the server, as do the server-wide volatile characteristics.
    
    > Note that you cannot change the subnet mask when the server has an
    > address; you must delete the address (CHANGE INTERNET ADDRESS NONE, I
    > think) and then change the mask and then re-configure the address.
    
    You cannot SET or CHANGE the MASK or ADDRESS once they exist. The 
    correct procedure is to DEFINE a new value for MASK and ADDRESS and
    reboot the server.  You can SET a MASK and ADDRESS only if there is
    *not* one DEFINE'd.  When SET'ing or CHANGE'ing the MASK and ADDRESS,
    always do the MASK first.
     
    Regards,
    
    Dave
    

    Do 
    
    show port x status
    
    the Output Signal should be DTR
    the Input Signal should be DSR RXD
    
    if this is not the case, you probably have a bad cable.  possible that
    the connector (H8571-J) is bad - but this is very unlikely.  This is 
    teh connector that you are using - it's the only one that works.
    
    It is not uncommon to have a cable problem.
    
    Sheila
    

    Thanks to everyone for your help.
    
    The customer generally makes up their own cables.  When I said the
    cable checked out they just tested that it could receive and send data. 
    When we looked at the cable spec it was not as shown in appendix A of
    the DEChub 900 owners manual.
    
    We also found that MUTISESSIONS should be disabled on the server port.
    
    Thanks again for the answers.
    
    John