| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 772.1 | | QUIVER::SLAWRENCE | | Mon Feb 28 1994 19:24 | 15 |
|
First of all, if you want to manage the hub you need to connect
directly to the OBM port on the hub, not to the DECserver900. The OBM
port is the 9pin connector on the agent (next to the RJ45 for the setup
port).
Your serial port must be 8 bits, 1 stop bit, No parity, and the
baud rate must match that configured using the Hub setup port (9600 by
default, but make it higher if your PC can do it).
If you're using a modem, then a standard PC-modem cable will work.
If your're trying to do a direct connection you need to use a 'modem
eliminator' that crosses DTR/DSR, CTS/RTS, and Tx/Rx; just as you would
if you wanted to connect two PCs together via the serial ports.
|
| 772.2 | But..... | WOTVAX::HATTOS | I think, Therefore I'm paid less | Tue Mar 01 1994 13:21 | 8 |
| OK,
given I have to do it this way, why does my SLIP connection die when I
go into windows?
Thanks anyway!
Stuart
|
| 772.4 | In-Band-Out-Of-Band Warning | QUIVER::SLAWRENCE | | Tue Mar 01 1994 19:22 | 23 |
|
A word of warning about:
> The setup in .0 should work:
> laptop -- H8571-J -- BN24h-03X -- DECserver
> You must use the hub's in-band ip address in this case.
We call this 'in-band-out-of-band'; your connection to the hub goes
through the SLIP line, but the packets must also go across the ethernet
backplane connection and through the repeater. This means a lot of
extra stuff that must be working for your management messages to get
through, and means that your management traffic is on the same network
as your users (which the original poster seemed concerned with).
While the above might (under normal circumstances) work, it would have
no advantages and several disadvantages over a direct connection to the
OBM port on the hub.
One case that you may run into is a hub that has no module capable of
acting as the IP Server (this should become less of a problem, as most
new modules will be able to do this). In that case, you can connect
a port on the terminal server to the OBM port and get to the agent that
way. Again, this is not really out-of-band.
|
| 772.5 | corrected .3 | QUIVER::ORSHAW | | Tue Mar 01 1994 19:48 | 47 |
| <<< KALI::$1$DUA3:[NOTES$LIBRARY]HUB_MGNT.NOTE;1 >>>
-< Hub Management Conference >-
================================================================================
Note 772.3 Hubwatch T2.8, SLIP connection dies, HELP! 3 of 4
QUIVER::ORSHAW 39 lines 1-MAR-1994 14:41
-< Some help... >-
--------------------------------------------------------------------------------
Here's some suggestions:
The setup in .0 should work:
laptop -- H8571-J -- BN24h-03X -- DECserver
You must use the hub's in-band ip address in this case.
.1 should also work:
laptop -- H8571-J -- DECconnect office cable -- H8571-J -- 900 hub
OBM port
You must use the hub's out-of-band ip address in this case.
Edit your pwtcp.ini file. In the [TCPIP] section, make sure the
NetworkType line is:
NetworkType=2
Edit your strtslip.bat file. Make sure the dllasync line is:
dllasynch /DATA_BUFFER_SIZE:1024
If your laptop has only one serial port, and you usually have the mouse
connected on that port, you won't be able to do much with hubwatch. You
must change your windows setup so that windows thinks you have no mouse
installed. Otherwise, windows will try to initialize the mouse when it
starts. It usually sets the DECserver back to local mode so further
slip communication will NOT work.
Lastly, if you have more than one serial port, try using slip on the
other port (comm2). We have had one case where slip would not work on
comm1 but worked fine on comm2. It was most likely some kind of
configuration problem on that pc but we couldn't find it.
Try installing pathworks 5.0 on your laptop. If you can run slip on
your comm port using pathworks, then hubwatch should work fine. If you
can't run using pathworks, then hubwatch will not run either. Perhaps
the pathworks people could be of more help at that point.
Jim
|