[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | FDDI - The Next Generation |
|
| Moderator: | NETCAD::STEFANI |
|
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
1878.0. "AS 1000's and DEFEA-DA's" by 49716::PAYERHUBER () Mon Nov 27 1995 06:57
Hello,
2 AS 1000 connected via DEFEA-da (a-b, b-a) and de435 (unbridged), no
other nodes on FDDI, intermittendly fail to start LAVC-communication
via FDDI, when one of the 2 nodes is booted.
DEFEA-DA,s are at FW 2.46 and in Full Duplex as shown by Lancp.
VMS is 6.2, latest Pedriver patch applied.
Systems boot from their own (unshadowed) systemdisk on SWXCR. Other
disks on the SWXCR (JBOD) are shadowed, and in the case of the failure
all the shadowcopy traffic is flooding the ethernet.
Are there any known problems in this area?
How to disable full duplex permanently via Lancp, I tried this with
Lancp, but after rebooting the Alphas the DEFEA's are in Full duplex
again.
Cheers, fritz
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1878.1 | | NETCAD::STEFANI | Machines to humanize | Mon Nov 27 1995 10:38 | 9 |
| >>How to disable full duplex permanently via Lancp, I tried this with
>>Lancp, but after rebooting the Alphas the DEFEA's are in Full duplex
>>again.
Both the DEFEA and DEFPA firmware power-up with FDX disabled, so the
driver or console firmware must be enabling it. I would look for some
sort of driver switch or similar parameter.
/l
|
| 1878.2 | the solution = Defea @ 2.46 | 49708::PAYERHUBER | | Tue Jan 30 1996 09:26 | 3 |
| My fault: in reality the DEFEAS were @ FW 2.3.
Upgrading to 2.46 solved the problem!
Cheers, fritz
|