| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2878.1 | Thanks for heads-up! | PTOJJD::DANZAK | Pittsburgher � | Thu Oct 19 1995 10:17 | 1 |
| Thanks, Steve for the heads-up! Regards, j
|
| 2878.2 | A workaround to get five Ethernets and the FDDI | NPSS::WADE | Network Systems Support | Thu Oct 19 1995 16:39 | 29 |
|
The following is a workaround for this if your customer ABSOLUTELY MUST
(you'll see why I say this later) have five, not six, Ethernets ports and
the FDDI port connected to the backplane.
- redirect four (any four except port 3) Ethernet ports to the back
- connect those four to your backplane Ethernet lans
- redirect the FDDI port and port 3 to the back
- connect the FDDI port to the FDDI lan and port 3 to the thinwire
Six out of seven isn't too bad but its better than four. And, as always,
there are some (actually two) gotchas. The first is that you need to
remember which backplane lans the four Ethernet ports are connected to as
they are now grouped into one pulldown stub. The second gotcha is the one
related to ABSOLUTELY MUST; if in the future you need to reconfigure
any Ethernet port except port 3 you need to do the following -
- disconnect the FDDI and port 3 from the FDDI lan and the thinwire
lan
- redirect the FDDI port and port 3 to the front.
- then the four Ethernet pulldown stubs can be independently
manipulated
Your customer most definitly won't like this part about
reconfiguring unless he absolutely needs five Ethernets and
the FDDI connected to the backplane.
Bill
|
| 2878.3 | Thanks for heads up | ANGLIN::BERNDT | | Fri Oct 20 1995 17:58 | 5 |
| Bill and Steve:
Thank you for the heads up... it really is nice to know about this
before the customer finds it, we can be more effective and proactive.
Ron Berndt
|
| 2878.4 | Patched version | STEVEV::VINGERHOET | | Tue Oct 31 1995 12:52 | 11 |
| I've created a new version (V4.1.2) of HUBwatch/Windows that should fix the
problem describe in the base note ONLY.
This version should ONLY be used to get around this problem. There are NO
plans at this time to release this version to SSB.
The kit can be copied from the anonymous FTP area on the node BHUB under
the directory "route_pc". The directions are similar to those provided in
Note #8.7.
Steve
|
| 2878.5 | what does 4.1.2 fix? | CSC32::J_SHUMWAY | | Wed Nov 01 1995 11:55 | 4 |
| I have installed V4.1.2. I see no difference. Double clicking the
module in the main screen or the Lan Interconnect screen launches
a telnet session. I can still only get 6 of 7 lans to the backplane.
What does this fix? Have I missed something?
|
| 2878.6 | use the expand button | CSC32::J_SHUMWAY | | Wed Nov 01 1995 12:21 | 4 |
| Oppps, if single click the module then click on expand, the Lan
Interconnect for the slot is displayed and can manage all ports.
thanks for the fix
|