T.R | Title | User | Personal Name | Date | Lines |
---|
2006.1 | | NETCAD::STEFANI | | Tue Apr 02 1996 22:27 | 21 |
| >> +---------------------+
>> | Cabletron MMAC Plus |
>> | with MM FDDI conc |
>> +---------------------+
>> | M M |
>> | |
>> | |
>> \ /
>> A \ / B
>> Alpha server 2100
>> DEFEA-DA (FW 2.46)
>> Digital Unix 3.2C
If the Cabletron ports are really advertising themselves as M-ports,
then I'd expect the DEFEA-DA B port to be solid green and the DEFEA-DA
A port to be alternating green/red.
If you're seeing flashing green on both ports, then it probably
indicates that you don't have crossover cables connected.
- Larry
|
2006.2 | not cable problem | DAIVC::RUDY_MA | | Tue Apr 02 1996 22:43 | 4 |
| we have already check our cable, with this cable we also try DAS
connection with another port (type A/B)and another devices, it works
normaly.
I think this not cable problem.
|
2006.3 | | NETCAD::STEFANI | | Tue Apr 02 1996 23:24 | 15 |
| OK. Try to connect just the B and M ports. Leave the A port on the
DEFEA unconnected. You should get a solid green LED on the B port
and flashing green on the A port.
If that works, disconnect the B port, then try the A-M port connection
and leave the B port unconnected. You should get a solid green LED on
the A port and flashing green on the B port.
If you can't duplicate the above behavior then you have a fundamental
problem not related to dual-homing. We know for a fact that the
DEFEA-DA supports dual-homing. One of my bigger customers (SG Warburg
- UK) dual-homes DEFEA's to Cabletron hubs. I don't know what model
hub, but I know it works.
/l
|
2006.4 | firmware | DAIVC::RUDY_MA | | Wed Apr 03 1996 09:02 | 8 |
| thank you for your suggestion and information,
could you tell me the version firmware of DEFEA-DA that already done in
UK ?
Because we have already try with firmware 2.3 and 2.46, and the problem
still does.
Do yo have any suggestion ?
rma-dan
|
2006.5 | | NETCAD::STEFANI | | Wed Apr 03 1996 14:04 | 18 |
| >>could you tell me the version firmware of DEFEA-DA that already done in
>>UK ?
Both 2.3 and 2.46 support dual-homing. The reason to upgrade to 2.46
is to avoid a problem where the adapter halts under heavy receive
traffic.
>>Do yo have any suggestion ?
I don't have any other suggestions. I'm confident that dual-homing
works, it always has. Your best bet now is to get someone who's very
familiar with low-level FDDI station management protocols and have them
see the traffic between the -DA and the hub when the link is being
brought up. Maybe they can see what's wrong. You can also try
dual-homing to a Digital concentrator or different make hub just to
see if the board is functioning properly.
-Larry
|