| 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 am trying to access a dechub 900 with hubwatch v3.1 through FDDI
without success. I have a XLserver 590 with a DEFPA PCI FDDI card with
Hubwatch running on it. This pc is plugged in to port 4 of a 900mx in
slot 8 of the backplane. When I ping the hub the ARP appears to fail, I
can deduce this because after failure I can connect to the hub with an
ethernet hubwatch client and see in the bridge addr tables the mac addr
of the DEFPA with a status of learned. After about 30 seconds the
status becomes inactive. So I must be sending packets. In the netstat/i
counters I get route not found error and 3 packets sent for every ping
attemp. If I mannually put the mac addr of the hub into the ARP table
the ping will give 0 route not found error and 3 packets sent.
Config: dechub 900 v3.1.0
slot 2 decbridge 90
slot 6 900tx
slot 7 900tx
slot 8 900mx management slot when hub was configured
Another interesting thing is the MAC addr (08-00-2b-xx-xx-xx) of the
hub never shows up in the bridge addr tables on either 900 tx. Which
makes me think the tx's are not forwarding and learning the hubs addr
properly. If someone knows if the hubs mac addr should show up I'd
appreciate a reply.
Any Ideas Welcome
Carey Lee
| T.R | Title | User | Personal Name | Date | Lines |
|---|