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 |
We are in a bit of a bind here, we need hubwatch for windows so we can turn the backplane port of a DB900MX on. Is there anyway that this can be done with what is on the net?? Why can't the DB900MX be sent to the field with these ports enabled out of the box? This would cure the critical problem we are up against now. We are in a customer situation where there is no VMS avalable anywhere on the net . The customer has bought 5 hubs and may be buying upward of 50 to 70 hubs. This could be a show stopper
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1270.1 | KAOFS::S_HYNDMAN | Acronym Decoder Ring Architect | Wed Aug 03 1994 14:35 | 10 | |
See note 1218. Your best bet is to bring your own Vax or stage everything first. Scott | |||||
1270.2 | SCCAT::SHERRILL | Wed Aug 03 1994 14:56 | 2 | ||
Swell | |||||
1270.3 | Note #651 Has More Details | DELNI::PIEPER | Thu Aug 11 1994 16:15 | 12 | |
Having the FDDI ports pointing to the backplane would not solve your problem either since you would still need HubWatch to tell those ports WHICH backplane channels to use. FDDI is NOT configured like Ethernets in the backplane. The Ethernet backplane channels are buses while FDDI connections are point to point. In other words channels 13 & 14 might be used to connect FDDI module #1 to FDDI module #2. Channels 11 & 12 might be used to connect FDDI module #3 to FDDI module #2 so we now have three stations in the FDDI network. It takes TWO backplane channels to interconnect any two FDDI modules across the backplane but we cannot default FDDI devices to any specific channel because it would cause havoc every time you plugged one of these modules into an existing FDDI network. |