| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| 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 |
Hi
We are trying to configure the following configuration using DEChub900
chasis using HUBwatch for VMS V3.0:
-------------------------
| | | | | | |
| | | | | | |
| 1 | 2 | 3 | | | |
| | | | | | |
| | | | | | |
-------------------------
slot1 - DECconcentrator 900MX
slot2 - DECbridge 900MX
slot3 - DECbridge 900MX
other slots - empty
The SNMP agent is on slot2 and one of the ports of slot 2 is connected
to the LAN.
We want:
1. The 3 cards will be connected on the internal (FDDI) bus.
2. The DECbridge 900MX will act as a 6 SAS interfaces (port 1 will not
be A and port 6 will not be B)
No errors were noticed during the instalation of the HUBwatch on the VMS
station.
While running the HubWatch - the 3 modules were detected right.
I have declaired a new FDDI lan and got it on the screen.
Draging the FIRST any module to the new FDDI line was OK.
Trying to drag the other two modules to the FDDI line was not permited
(no matter which module was the first one and which 2 modules were the
last).
At last I made the connection between 2 modules using external MIC/MIC
cable between the modules.
Another problem I had: although the SNMP agent is on slot 2 - I can see
all the information on the module which is in slot 1 but I can not get the
information on the module which is in slot 2 although it is the SNMP agent.
Ilan Alter
Israel
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1271.1 | Check hardware rev of bridges.... | NACAD2::BATTERSBY | Thu Aug 04 1994 09:39 | 12 | |
I'd suggest doing a re-direct to one of the DECbridge 900MX
cards, and then show current settings. You should see the
first line in the menu response that looks like the following
DECbridge 900MX, 6-Ethernet/FDDI Bridge, HW=v0/1,RO=v0.2,SW=v1.2.1
^^^^^^^
Take a close look at the hardware rev of both the bridges. If you
have a hardware rev (HW=v0/0), then you have bridges that don't support
backplane LAN hopping 100%. this may be your problem.
Hardware rev of HW=v0/1 will support backplane LAN hopping.
Bob
| |||||