T.R | Title | User | Personal Name | Date | Lines |
---|
3808.1 | Not the lastest firmware on gatekeeper | NYOSS1::HERENDEEN | Tom Herendeen, 508-888-3239 | Fri Aug 23 1996 23:38 | 16 |
| don't use gatekeeper.dec.com the firmware is ALWAYS out of date.
use http://www.networks.digital.com/dr/hubs/firmware/ if you are out
side the firewall. Inside the firewall, use
http://npbww2.hpn.lkg.dec.com/dr/hubs/firmware/. After you pull down
any new firmware, don't forget to modify your DCFFILE.DAT file too.
The other thing I should ask you is if you created your backplane FDDI
ring in the LAN interconnect view. I had some problems with the DEFBA
V1.5.2 and the DEF6X V2.x until I created the ring.
What version of HW/MCM are you using?
Good luck
Tom Herendeen
NPB SE
|
3808.2 | Versions and config informaiton | SCASS1::EWISE | Pobodys Nerfect | Sat Aug 24 1996 19:39 | 12 |
| Re .-1
I used http://www.networks.digital.com/dr/hubs/firmware/ and I updated
my DCFFILE.DAT file.
I created my FDDI Ring in the LAN interconnect view.
I am using clearVISN version 5.0
DEF6M is version 3.24 and defba version 1.61 HUB900 version 4.20
Thanks... Still looking for the something stupid I've done.
Efw
|
3808.3 | | NETCAD::DOODY | Michael Doody | Mon Aug 26 1996 11:06 | 21 |
| >When I drag the B on the DEFBA to the FDDI ring in the DEChub900 it connects
>fine. It then states that I should drag the other side of the ring right away.
Actually, it connects the port on the screen, but has not told the hub anything
yet. Only when the second connection is made does MCM transmit the connect
request to the hub.
>I clear this message box and try to drag the port on the DEF6M to the internal
>FDDI ring. The ring IS NOT grayed out and when I release the connection it
>sticks to the line and the ring colors match. after about 15 seconds I get an
>Add Failed message.
When you get the add failed message, is there supporting information in the
message box?
Are these the only two modules in the hub? So there is no backplane contention.
Is it possible that you are using the read-only community string, when you
should be using the read-write community string?
-mike
|
3808.4 | More Facts | SCASS1::EWISE | Pobodys Nerfect | Mon Aug 26 1996 14:10 | 11 |
| re .3
The message box only states "Add Failed"
"public" is the Read/Write name
Other modules are in and or out depending on my which of the multiple
configurations I have tried. I have tried two Backplanes as well.
Efw
Still lost in the Ether
|
3808.5 | need more info | NETCAD::CURRIER | | Tue Aug 27 1996 11:16 | 6 |
| Please describe all the LAN backplane connections that exist prior to your
attempt to connect the FDDI ports to the backplane.
-sheila
|
3808.6 | Slim Pickins' | SCASS1::EWISE | Pobodys Nerfect | Tue Aug 27 1996 12:26 | 5 |
| Default Thinwire that is always present.
New FDDI Ring.
That is all...
Efw
|
3808.7 | my $.02 | CSC32::D_PERRIN | | Fri Aug 30 1996 18:00 | 5 |
| It looks like you are doing everything right. FWIW, I see that you've
tried two backplanes, but I recently had a hub that was behaving very
strangely when I tried to make backplane connections and doing a
"reset to factory" was the only thing that cured it. Just something
else to try. Ditto on both modules.
|
3808.8 | Ring is Fine | SCASS1::EWISE | Pobodys Nerfect | Fri Sep 13 1996 16:53 | 10
|