| 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 |
I recently had a problem with a DH 900, DC 900MX and DS 900EF config.
Customer has 2 DH 900's with a DC 900MX and DS 900EF in each hub.
Hub #1
DS 900EF slot 8
DC 900MX slot 7
Hub firmware upgraded to V4.1(hub), V1.52(900EF) and V3.11 (900MX).
Configured the following FDDI ports on the units:
900EF A front panel
B backplane
Joined B and A, respectively thru the backplane while A and B goes out
to the site DAS ring.
Hub #2
DS 900EF slot 2
DC 900MX slot 3
Upgraded all modules to the same rev levels as Hub #1. Tried the same
A/B connections as Hub #1 but Hubwatch returned with an ADD FAILED
message. It didn't matter whether the 900MX leg was attached first to
the hub FDDI or the 900EF. When the second leg was joined to the ring
it did not stick and the error message was returned.
The only way A's and B's would work is if the 900MX had both A and B
into the back and then either A or B from the 900EF was added. I could
not do B from one and A from the other or visa versa.
The config was left at 900MX A and B to the front with a M to the back.
The 900EF then had a S to the back. It seems to be working fine but
the customer doesn't want both A and B on the 900MX. If it fails then
the 900EF loses ring access.
Any guesses?
dave
the 900EF
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3014.1 | NETCAD::DOODY | Michael Doody | Wed Nov 29 1995 12:54 | 9 | |
Hate to say it but you might try resetting the hub (MAM). Try "reset to
current" first, if that doesn't work try "reset to factory" and you
will then have to re-create the configuration.
Also, when you see strange things like this you should try doing a
refresh on the LAN Interconnect screen of Hubwatch.
If any of this works, please let me know.
-Mike
| |||||
| 3014.2 | Why not, nothing else makes sense. | CGOS01::DMARLOWE | Have you been HUBbed lately? | Wed Nov 29 1995 15:47 | 10 |
Mike,
Yea I did a refresh (several times) but kept coming up with the same
error. I'll ask the customer to do a RESET WITH CURRENT and let you
know. Hopefully it won't need a RESET TO FACTORY. 8^(
It may take a while as it is a particle accelerator and they don't get
a lot of down time as they run 24 x 7.
dave
| |||||
| 3014.3 | Is reset safe...? | LEMAN::PAIVA | Hawkeye - Network Support @GEO | Mon Dec 04 1995 04:21 | 4 |
Normally (;-), resetting the HUB900MS does NOT affect your connections,
but you're right to be cautious...
Pedro
| |||||
| 3014.4 | Problem resolution - reset to factory. | CGOS01::DMARLOWE | Have you been HUBbed lately? | Fri Dec 15 1995 12:03 | 10 |
The customer didn't really want to do a reset to factory so only tried
a reset with current. Needless to say the problem remained.
After writing down the IP address, name, location and contacts, I did a
reset to factory. Put everything back in, did the ligo's and now have
the hub on the dual ring.
Moral of the story: When nothing makes sense, do a reset to factory.
dave
| |||||