[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
1820.0. "900MX 4th port blank even with PMD in it" by PTOJJD::DANZAK (Pittsburgher �) Fri Dec 23 1994 08:52
I have a customer who has a 900EF and 900MX in two ONEhubs. Currently
only port B of the EF is connected to port A of the MX, so the FDDI
between the two is wrapped. Off of port 2 of the MX we have an FDDI
attached device. All other ports of the MX are vacant. The EF has
only one port in use to the management station - a PC running HUBwatch
for Windows V3.1. I assigned IP addresses to both the EF and MX and
used HUBwatch to view them. Note that the bottom port (B) on the MX
has no PMD - the customer only needs a single connection, yet the MX is
configured as the default (A&B) via the front ports.
When viewing the MX, the 4th port CONSISTENTLY shows port 4 as blank.
All green but blank - no PMD. We attached the one FDDI station to it
and it appears to work.
WHY would HUBwatch show a blank PMD even though one was there? Could
it be that we have no PMD in the 6th port and an A/B config? To test
things out I changed PMDs between the 5th and 4th port. (Bad PMD?) but
the result was the same. Could the 4th port on the MX board be bad?
Could there be a problem in Hubwatch ? (naaw...(grin))
Any ideas?
Thanks,
j
T.R | Title | User | Personal Name | Date | Lines
|
---|