| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1022.1 | DRAFT - FBUS/FDDI Sales Update | DELNI::G_NIELSEN | | Fri Sep 17 1993 11:57 | 177 |
|
DEC FDDIcontroller/FUTUREBUS+ Open Systems Network Interface Card
CONTACT
George Nielsen DTN: 226-5510, (508)486-5510, LKG2-1/W06
HIGHLIGHTS
* Provides FDDI connectivity for Digital's DEC 4000, and alternative FDDI
connectivity for DEC 7000/10000 w/FUTUREBUS+ I/O Backplane Option
* Includes SMT V7.2 for continued multi-vendor Interoperability, and uses
DMA transfers on both transmit and receive to minimize CPU overhead
* Supported by OpenVMS AXP V1.5 or later, and OSF/1 V1.3 or later
CUSTOMER PROBLEM
o Need for high bandwidth FDDI local area network connectivity on DEC 4000,
or alternative FDDI Connectivity on DEC 7000 and 10000
o Requires Dual Attachment Station (DAS) option to support connecting Servers
directly in an FDDI dual ring without a wiring concentrator or hub, or as
as "dual-homed" connection to two wiring concentrators
o Requires Single Attachment Station (SAS) option to simplify end-user station
management and to isolate the backbone from end-user reconfiguration
disruptions
o Requires extended distance (>2KM) between stations to support for example:
fault tolerant, or multi-datacenter configurations
DIGITAL SOLUTION
The DEC FDDIcontroller/FUTUREBUS+ provides FUTUREBUS+ to FDDI connectivity
for Digital CPUs, and Third Party Products equipped with a Profile "B"
Futurebus.
This adapter is configurable as either a SAS or DAS option, and supports both
Multi-Mode Fiber for up to 2KM between stations, and Single-Mode Fiber (SMF)
for distances up to 40KM between stations.
CUSTOMER BENEFITS
o Extends FDDI connectivity to the DEC 4000 family of CPUs
o Provides enhanced reliability and availability via support for dual
homing, and an external 3rd party optical bypass relay - (DAS only)
o Provides the highest aggregate throughput, in excess of 100 Megabits/Sec,
when operated in Full-Duplex Mode. Full-Duplex allows it to connect Point-
to-Point with another Digital FDDI adapter (except DEFZA) or to Digital's
GigaSwitch, and operate without a token. Operating without a token
eliminates the latencies associated with waiting for the token to transmit,
and allows simultaneous transmit and receive at aggregate data rates in
excess of 100 Megabits/Sec.
COMPETITIVE COMPARISON
As of this writing there are no other known suppliers for Futurebus to FDDI
adapters. The competition for this controller will be indirect at the system
level, and will involve other I/O bus types.
Digital's competitive strengths include:
o A portfolio of high performance, high reliability FDDI controllers for
PCs, workstations, servers, and multi-user high-end systems (EISA, Q-bus,
TURBOchnl, XMI-Bus, and now Profile "B" Futurebus)
o Full-Duplex mode to provide aggregate bandwidths in excess of 100 Megabits
per Second
o In combination with Digital's GigaSwitch, extends the range of FDDI
applications by supporting scaleable bandwidth, switched network technology
o Complete solution vendor
o FDDI technology leader
o System integrator for multi-vendor networks
o Worldwide network of support
CHANNELS STRATEGY
The DEC FDDIcontroller/FUTUREBUS+ will be sold by the Digital direct sales-
force, and can also be sold by Digital's Business Partners including: VARs,
Developers, Distributors, Master Resellers, Integrators, and Technical OEMs.
PRICING/ORDERING INFORMATION
Model No. Description Quantity MLP Disc OEM BMC Inst
--------- ---------------------------- -------- ------ ---- --- --- ----
* MMF Pre-Configured Options (w/MIC connectors):
DEFAA-AA FBUS+ to FDDI Adptr SAS, MMF C2 $8,995 3 X $46 $600
DEFAA-DA FBUS+ to FDDI Adptr DAS, MMF C2 $9,995 3 X $52 $600
* SMF Configurable Option:
DEFAA-YA FBUS+ to FDDI Adapter wo/PMDs C2 $8,295 3 X $40 $600
NOTE: At least (1) DEFXS-AA must be ordered with each DEFAA-YA. A maximum
of (2) MODPMDs can be ordered with each -YA. The MODPMDs associated
with each DEFAA-YA must be listed immediately after the -YA on the
customers P.O.. The first MODPMD listed after the -YA will be
installed in the "B" port forming a SAS adapter. The second MODPMD,
if listed, will be installed in the "A" port forming a DAS adapter.
(-YA) Supported MODPMDs
DEFXS-AA Single-Mode-Fiber (SMF) PMD
DEFXM-AA Multi-Mode Fiber (MMF) PMD
o Patch Cables are NOT included! (Listed for reference)
BN24B-xx, MIC to MIC; BN24D-xx, MIC to ST
o Optical Bypass Relay for use with MMF ONLY, is NOT available from Digital
(Listed for reference)
AMP 501916-3 (w/6 pin Modular Jack Connector)
SERVICES
The normal portfolio of hardware, Operating System OpenVMS AXP and OSF/1
service offerings are available. For further information please contact your
local Digital Services representative.
TECHNICAL DATA
Like it predecessors, the DEC FDDIcontroller/FUTUREBUS+ utilizes electrically
programmable FLASH ROM to hold its functional firmware and diagnostics. In the
event a need develops to update the adapter's on-board firmware, the ALPHA
LFU utility CDROM will be updated to include the new firmware.
CONFIGURATION INFORMATION
Hardware Requirements & Configuration Rules
o DEC 4000, or DEC 7000/10000 equipped with the optional FBUS+ I/O backplane
o One Futurebus Profile "B" Slot
o Number of controllers supported per Digital System = 2
Software Requirements:
o OpenVMS AXP V1.5 or later, or OSF/1 V1.3 or later
Configuration Restrictions:
o OpenVMS - There is a statistical probability that when two CPUs are
connected point-to-point, and both CPUs are running VMS, that they
will NOT connect. For this reason, this configuration is NOT supported
at this time. This restriction will be removed with the next release
of OpenVMS.
RESOURCES
o Internal
FDDI Notes File, Including:
DEFAA OpenVMS AXP V1.5 Start-Up Release Notes
DEFAA OSF/1 V1.3 Start-Up Release Notes
Pre-Requisite DEC 4000/7000/10000 HW, Console, etc. Rev/Ver
DEC 4000 Console Edits to support FBUS+
o External
Contact George Nielsen
TRADEMARKS
AMP
|
| 1022.2 | DEC 7000/10000 Min HW Rev To Support FBUS | DELNI::G_NIELSEN | | Fri Sep 17 1993 12:34 | 26 |
|
DEC 7000/10000
==============
Description Part# Minimum Rev/Version
------------------------------ -------------- -------------------
CPU E2040-AA M06
Memory
64MB E2043-AL D01
128MB E2043-BL D01
256MB E2043-CL D01
512MB E2046-AA D01
IOP E2044-AA F04
Firmware
Console and Palcode AVMS V2.4/V2.5
Console and Palcode AOSF V2.4/V2.5
DWLAA-AA
Futurebus Backplane/Cardcage BA653-AA D01
Flag Module B2003-AA B01
|
| 1022.3 | DEC 4000 (610, 710, 720) Min HW Rev To Support FBUS | DELNI::G_NIELSEN | | Fri Sep 17 1993 12:43 | 39 |
|
DEC 4000
========
Single Processor
----------------
Description Part# Minimum Rev/Version
------------------------------ -------------- -------------------
CPU
COBRA Model 610 B2001-BA B02 (1/System)
FANG Model 710 B2012-AA A01 (1/System)
Memory
64MB B2002-CA B01
128MB B2002-DA B01
I/O Module (1 per system)
DSSI/SCSI I/O Module B2101-AA H01
FAST SCSI I/O Module B2101-BA A01
Firmware V3.2
SMP
---
Description Part# Minimum Rev/Version
------------------------------ -------------- -------------------
CPU
COBRA Model 610 B2001-BA B02 (2/System)
FANG Model 720 B2012-AA A01 (2/System)
Memory
64MB B2002-CA C01
128MB B2002-DA C01
I/O Module (1 per system)
DSSI/SCSI I/O Module B2101-AA H01
FAST SCSI I/O Module B2101-BA A01
Firmware V3.2
|
| 1022.4 | MANDATORY DEC 4000 nvRAM Patch To Support FBUS | DELNI::G_NIELSEN | | Fri Sep 17 1993 12:58 | 28 |
| When a Futurebus device attempts to use the last page in memory, it may
pre-fetch past the last page into non-existent memory, causing VMS to crash. A
permanent fix in a future release will be to make the last page of memory
reserved to the console.
For this release, a work around is available that will reduce the number of
pages available by one. To install this fix you need to edit two commands into
the NVRAM as follows:
>>>edit nvram
editing `nvram'
0 bytes read in
*1 set x `e -p -q 2940 | find 2`
*2 d -p -q 2940 `eval -x -ix $x 1 -`
*exit
64 bytes written out to nvram
>>>
You can verify the information by doing a "cat nvram".
>>>cat nvram
set x `e -p -q 2940 | find 2`
d -p -q 2940 `eval -x -ix $x 1 -`
>>>
Now when you reboot or init your console, the commands in NVRAM will execute
thus reducing the page count by one.
|
| 1022.5 | | JEDI::CAUDILL | Kelly - Net Tech Support - 226-6815 | Fri Sep 17 1993 17:18 | 7 |
| It would be nice if we could have some description of the crash that is
caused by this.
I've run Cobra with FDDI and I don't think .0 has been done to the
Cobra but I didn't have any crashes (that we not found to be the fault
of something else which has since been fixed). So I wonder when this
happens etc...
|
| 1022.6 | | NETRIX::thomas | The Code Warrior | Fri Sep 17 1993 18:35 | 1 |
| I also wonder if it happens under OSF/1... but, so far, NETRIX hasn't seen it.
|
| 1022.7 | Configuring OSF/1 V1.3 to use DEFAA | DELNI::G_NIELSEN | | Thu Sep 23 1993 13:21 | 59 |
| INSTRUCTIONS FOR CONFIGURING DEFAA (FBUS-TO-FDDI ADAPTER) ON DEC OSF/1
- ----------------------------------------------------------------------
(Revision 93Jun15)
Applicable DEC OSF/1 Versions:
OSF/1 T1.3-4 (Rev. 80.2) [Silver/Maintenance BL4].
1. Add the following lines to /sys/conf/alpha/files:
io/dec/netif/if_faa.c optional faa device-driver Binary
data/if_faa_data.c optional faa Notbinary
2. For DEC7000 systems,
add the following lines to /sys/conf/<user's config file>:
bus fbus0 at iop0 vector fbuserror
controller faa0 at * vector faaintr
controller faa1 at * vector faaintr
controller faa2 at * vector faaintr
controller faa3 at * vector faaintr
For DEC4000 systems,
add the following lines to /sys/conf/<user's config file>:
bus fbus0 at ibus0 vector fbuserror
controller faa0 at * vector faaintr
controller faa1 at * vector faaintr
controller faa2 at * vector faaintr
controller faa3 at * vector faaintr
3. Edit /etc/rc.config.
(Note: This step is necessary because
netsetup does not yet support faa.)
The following variables are relevant:
NUM_NETCONFIG="1"
NETDEV_0="faa0"
NETDEV_1=
IFCONFIG_0="16.140.32.130 netmask 255.255.255.0"
IFCONFIG_1=
NUM_NETCONFIG is the number of network devices.
For each device, set NETDEV_x and IFCONFIG_x appropriately,
where x is the network device number.
NETDEV_x is the device name.
IFCONFIG_x is the value passed to the ifconfig command and
should have at least the network address and netmask.
Also in /etc/rc.config,
If your system uses routed or gated,
set these variables as appropriate:
ROUTED="yes"
ROUTED_FLAGS="-q"
ROUTER="no"
GATED="no"
GATED_FLAGS=
4. Rebuild the kernel using standard procedures.
5. Reboot the system with the new kernel using standard procedures.
|
| 1022.8 | Configuring OpenVMS AXP V1.5 to use DEFAA | DELNI::G_NIELSEN | | Thu Sep 23 1993 15:38 | 18 |
| OpenVMS AXP Version 1.5 supports a new FDDI LAN device that connects to
the Futurebus+, the DEFAA. The QIO interface to the DEFAA is the same as
as that described for the DEMFA in Chapter 6 of the VMS I/O User's Reference
Manual: Part II, except that the device type of the DEFAA is DT$_FA_DEFAA
(56 decimal).
The DEFAA is supported by SYS$FADRIVER. Its device name is;
FAcu
where c is the controller and u is the unit number (for example, FAA0).
The NCP LINE and CIRCUIT name for the DEFAA controller is:
FAA-<controller number>
(for example, FAA-0 for FAAn, FAA-1 for FABn).
|
| 1022.9 | | NETRIX::thomas | The Code Warrior | Thu Sep 23 1993 16:44 | 1 |
| For SSB V1.3 skip step 1 as the lines are already present.
|
| 1022.10 | Configuring OpenVMS to use Large Packets | DELNI::G_NIELSEN | | Fri Sep 24 1993 10:53 | 5 |
| To enable large packets on the FDDI adaters the SYSGEN parameter
LRPSIZE should be set to 4530. On OpenVMS AXP 1.5 and OpenVMS VAX 6.0 this
parameter goes away and a new parameter NISCS_MAX_PKTSZ controls the
maximum size of the packets. The proper value for NISCS_MAX_PKTSZ in those
cases would be 4468.
|
| 1022.11 | Announce and Availability Dates | DELNI::G_NIELSEN | | Fri Sep 24 1993 14:48 | 4 |
| The DEFAA options will appear on the Price File and On-Line Sales
Update on 4-OCT-93.
There will be limited availability in OCT-93, with volume in NOV-93.
|
| 1022.12 | | JEDI::CAUDILL | Kelly - Net Tech Support - 226-6815 | Tue Sep 28 1993 09:44 | 16 |
| re: .10:
> To enable large packets on the FDDI adaters the SYSGEN parameter
> LRPSIZE should be set to 4530. On OpenVMS AXP 1.5 and OpenVMS VAX 6.0 this
> parameter goes away and a new parameter NISCS_MAX_PKTSZ controls the...
Which protocols will these parameters effect?
DECnet PhaseIV will not use the larger packet size even if you set this
parameter, right?
TCP/IP will use the larger packet size even if this parameter is not set.
You would not want LAT to ever use the larger packet size because then
it would not get thru a 10/100 bridge and I don't know of any terminal
servers that live on FDDI.
|
| 1022.13 | LAT is not just for terminal servers any more! | ROYALT::RASPUZZI | Michael Raspuzzi - LAT Engineering et al | Tue Sep 28 1993 17:42 | 12 |
| � You would not want LAT to ever use the larger packet size because then
� it would not get thru a 10/100 bridge and I don't know of any terminal
� servers that live on FDDI.
What about SET HOST /LAT from VMS system to VMS system? What if we added
the LAT transport for DECwindows and allowed SET DISPLAY/TRANSPORT=LAT from
VMS to VMS? Then you might want large packet support.
Currently, LAT does not negotiate large packet support (yet) but it
is coming!
Mike
|
| 1022.14 | | JEDI::CAUDILL | Kelly - Net Tech Support - 226-6815 | Wed Sep 29 1993 14:21 | 4 |
| Yea, yea. I knew I would regret using LAT as an example.
What about the other protocols? Which ones are effected by this
parameters.
|
| 1022.15 | Clusters and Larger Packet Sizes | DELNI::G_NIELSEN | | Mon Oct 04 1993 14:12 | 3 |
| FDDI connected clusters will benefit the most from the larger packet
sizes.
|
| 1022.16 | DEC 7000 FBUS Slot Restrictions | DELNI::G_NIELSEN | | Mon Oct 04 1993 14:15 | 5 |
| Do not plug the DEFAA into Node "A"/Slot 10 of the DEC 7000 FBUS
Backplane. There is a known console bug that shows up during startup -
DECnet hangs.
This will be fixed in a future console release.
|
| 1022.17 | Statistical probability ? | SUBURB::JASPERT | | Tue Mar 08 1994 06:33 | 17 |
|
<< Configuration Restrictions
o OpenVMS - there is a statistical probability when two CPUs are
connected point-to-point, and both CPUs are running VMS,
that they will not connect. For this reason, this
configuration is not supported at this time. This
restriction will be removed with the next release of
OpenVMS. >>
What does this mean ? This is exactly what my customer wants to do,
is there a workaround ?
Tony Jasper, Partners Sales Support.
|
| 1022.18 | | KONING::KONING | Paul Koning, B-16504 | Wed Mar 09 1994 12:31 | 5 |
| If you put a concentrator between the two, it will work.
Does anyone know the current status of this bugfix?
paul
|
| 1022.19 | DEFAA on OSF/1 V2 on Cobra? What rev of DEFAA? | JEDI::CAUDILL | Kelly - Net Tech Support - 226-6815 | Tue Apr 05 1994 17:56 | 23 |
| Do you have to do anything special with DEC OSF/1 V2.0 or is all the
right stuff in the operating system now?
I installed OSF/1 V2 off the CD and ran netsetup and configured faa0
and it was fine. Or at least I thought it was. I didn't do any big
tests of it. I just used telnet to log into the system over the net
and it worked and so I went on to something else.
But now I've come back and it has been rebooted and the faa0 didn't
come up with the reboot. It is configured, but it isn't working - the
board didn't initialize - the phy light is not on. So I did
ifconfig faa0 down
ifconfig faa0 up
and it came up and I can talk to it now. But now I'm getting all these
faa0: Nothing on the command response queue.
messages on the console whenever anything happens over the net.
When the defaa initializes during startup, it reports firmware rev 0.4.
Is this (part of) the problem??
|
| 1022.20 | | JEDI::CAUDILL | Kelly - Net Tech Support - 226-6815 | Wed Apr 06 1994 12:30 | 14 |
| Gee, I had the sollution to my problem already.
Current DEFAA firmware seems to be V1.0b.
It's on the firmware CD with all the other firmware. What a great idea!
I booted the CD with:
>>> boot -fl 0,a0 dke100
filename: [dec4000]cfw_v33_updp3.exe
and eventually got a UPD> prompt and the list command showed me where
the DEFAAs were and that they were running 0.4 and the update command
updated them. There is online help and there is documentation on the CD.
|
| 1022.21 | I thought I was all set | JEDI::CAUDILL | Kelly - Net Tech Support - 226-6815 | Wed Apr 06 1994 14:05 | 24 |
| <<< MAY11::MAY11_USER:[NOTES$LIBRARY]COBRA.NOTE;2 >>>
-< Cobra >-
================================================================================
Note 206.0 updating DEFAA firmware No replies
JEDI::CAUDILL "Kelly - Net Tech Support - 226-6815" 17 lines 6-APR-1994 13:05
--------------------------------------------------------------------------------
I'm trying to update the firmware two DEFAA (FDDI) adapters
in a DEC4000/610.
The DEFAAs have V0.4 in them now.
I've got the V2.7 firmware CD (ie the one with the V3.3 firmware)
and I boot [dec4000]cfw_v33_updp3.exe and I updated the IO module just
fine but when I try to update either of the DEFAAs, it says:
DO NOT ABORT!
fbf0 Updateing to ...
and then sits there fore 5 or 10 minutes and then says FAILED.
What does this mean??? What do I do now?
|
| 1022.22 | answer to reply # 21 | MAY21::HUTCHESON | the revolution will not be televised | Fri Apr 08 1994 14:42 | 23 |
| This reponse to reply #21 was orginally entered in MAY21::COBRA
Note 206.1
Note 206.1 updating DEFAA firware
1 of 1
MAY21::HUTCHESON "the revolution will not be televi" 10 lines
8-APR-1994 13:34
-< Pass 2 DEFAA req'd for Update to 1.0 >-
Since your DEFAA contains V0.4 firmware, it must be a pass 1 module
with only 2 flash roms on it. The current hardware rev is pass 2
with
4 flash roms. This hardware rev, the only one supported by the
update
utility, would update from 0.8 to 1.0.
In other words, your DEFAA is out of date and you need a pass 2
version
in order to update the firmware.
Susan Hutcheson
|
| 1022.23 | duuuuhhhh | JEDI::CAUDILL | Kelly - Net Tech Support - 226-6815 | Sat Apr 09 1994 10:39 | 19 |
| <<< MAY11::MAY11_USER:[NOTES$LIBRARY]COBRA.NOTE;2 >>>
-< Cobra >-
================================================================================
Note 206.2 updating DEFAA firware 2 of 2
JEDI::CAUDILL "Kelly - Net Tech Support - 226-6815" 12 lines 9-APR-1994 09:38
-< sometimes things go very smoothly - but mostly not >-
--------------------------------------------------------------------------------
Someone took my DEFAAs away and updated the firmware via the interface
on the board. Now they are V1.0. We glanced at the boards as we were
putting them back in and I *think* I recall seeing 4 flash roms.
We tried them again and got the same error message and less success and
decided to give up and use ethernet until we can acquire production DEFAA
units. But this morning, as I lay thinking I should be sleeping at
6:00 am on a Saturday, I realized that we never connected the FDDI when
we tested them the second time. Have you ever had one of those lives?
One appears to be working fine at the moment, but PATHWORKS is still
using the ethernet so I won't say the testing is concluded. Sigh.
|
| 1022.24 | Does the DEFAA-YA support a UTP copper PMD ? | OURGNG::RIGGEN | Jeff Riggen "Sales Support" I think ? | Thu Jun 30 1994 13:01 | 19 |
| From the Sales Update:
********************************************************************************
DEFAA-YA FBUS+ to FDDI Adapter wo/PMDs
NOTE: At least (1) DEFXS-AA must be ordered with each DEFAA-YA. A maximum
of (2) MODPMDs can be ordered with each -YA. The MODPMDs associated
with each DEFAA-YA must be listed immediately after the -YA on the
customers P.O.. The first MODPMD listed after the -YA will be
installed in the "B" port forming a SAS adapter. The second MODPMD,
if listed, will be installed in the "A" port forming a DAS adapter.
(-YA) Supported MODPMDs
DEFXS-AA Single-Mode-Fiber (SMF) PMD
DEFXM-AA Multi-Mode Fiber (MMF) PMD
********************************************************************************
Has testing been completed on the DEFXU-AA PMD for a UYP Copper connection ?
Jeff
|
| 1022.25 | V1.0b or V1.1 firmware for DEFAA | CSC32::M_HERODOTUS | Mario at CXO3/B10 Colorado | Sun May 26 1996 09:11 | 9 |
|
I've heard of V1.0b and V1.1 firmware for the DEFAA controller. Do
these really exist and can someone point me to them. The V3.5 firmware
update CDROM contains V1.0
Also can anyone tell me what difference the V1.0b and V1.1 firmware
might make and what reasons there are for and against updating.
Thanks, Mario
|