| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1528.1 | Example setup. | HGOVC::SIUKEUNGLEE | | Wed Oct 05 1994 12:58 | 36 |
| Hello Henk,
Try the following steps:
You may need a DECrepeater 900TM (DETMM-MA) for tempory setup uses.
Or, you may have a cable connect between DEC90FA and DECBridge 900.
1) Connect a 10baseT cable between DECBridge 900 and DECrepeater 900.
2) Using DECHub900 console terminal to set the IP address of HUB900 and set
the management slot to DECrepeater 900.
3) Start Hubwatch and click the DECBridge 900 module. Then click the ports
setup icon and set the port 3 to blackplane.
4) Click the interconnect icon and move the port 3 to thinwire segment.
5) Reset the modules with current setting.
6) Try to ping the HUB900 again, it should work.
7) Reset the IP address of the HUB900 and set the management slot to
DECBridge 900. Reset with current setting.
8) Now you can remove the cable between Bridge and Repeater and see it
work.
IT work fine in our customer site.
Good Luck!
David
HKMCS
|
| 1528.2 | No - PROXY thru DEC900-EF (.aka. DECbridge 900MX)? | BELMNT::BEAZLEY | | Wed Oct 05 1994 14:14 | 6 |
|
RE. 1
Does this mean that a DECbridge 900-EF is not suitable as a 900MS Proxy?
|
| 1528.3 | DECbridge 900EF must have its own IP address I believe | NETCAD::BATTERSBY | | Wed Oct 05 1994 14:58 | 6 |
| I believe that if the DECswitch 900EF (DECbridge 900MX) doesn't
have an in-band IP address assigned to itself, you won't get
any response when you try to ping it. This is my personal observation
in our HUB Engineering Lab here in LKG.
Bob
|
| 1528.4 | litte more explanation | HLRG02::NOTES | Opel Manta | Fri Oct 07 1994 08:49 | 21 |
| Thanks for the reply's.
I did asign a TCPIP address to both the two bridges and the 900MS.
I configured the two bridges (connecting port 3 and port 1 of bridge one to
the backplane and connecting port 1 of bridge two to the backplane)
So bridge one is connected to an ethernet segment where the 90FA also is
connected to.
And both bridges are connected via port 1 to a FDDI flex-channel.
The segment where the PC is connected to is connected to one of the ethernet
ports of the bridges.
From the PC I can run HUBwatch but CAN'T ping to the 900MX or 900MS.
This is not really a problem (HUBwatch is running fine) but at least it is a
strange behaviour.
Just curious about this.
/-/ Henk.
|
| 1528.5 | more info | NETCAD::CURRIER | | Fri Oct 07 1994 11:40 | 27 |
| Hubwatch 'talks' SNMP. SNMP/UDP/IP... So if hubwatch is working - IP
is working. Can you ping the IP address that you started hubwatch
with. Re the other problems, please enter a diagram of your hub & lan
connections.
eg
FA MX1 MX2
------ ------ ------
| | | | | |
| | | | | |
------ ------ ------
o o o o
| | | |
| | | |
T/W----------- | -------------- | |--------------- | ---------
| | | |
E1 ------------o----------------o |--------------- | --------
| |
F1 -------------------------------o----------------o
is this an accurate picture? Where exactly is the wire from your
PC connected in the picture?
|
| 1528.6 | | NETCAD::ANIL | | Fri Oct 07 1994 21:05 | 5 |
| The bridge (or any other module) cannot serve the OBM address. If
you are using the same IP address for out-of-band management access as
for in-band management, that might explain some of what's going on.
Anil
|