| > Q2. I heard several months ago that switch from FDDI to FDX is
> done by setting MIB via SNMP. FDX to FDDI is done automatically.
> But FDX program summary says that both of FDDI <--> FDX are
> done automatically. Which is correct ?
Both. Use the MIB to *inhibit* full-duplex operation. If you enable
FDX in the MIB, then it turns on and off automatically depending on
your FDDI topology.
> Q3. Is DECconcentrator implemented FDX ?
Not possible. Full-duplex requires point-to-point links, not token
rings. Replace DECconcentrator with GIGAswitch to convert the single
token ring into a set of independent pt-pt links (or smaller rings).
|
| >> Q1. So far all of DEC's FDDI adapters(latest version) has FDX
>> implementation. Is this correct ?
Can't speak for all of them, but I know the DEFEA supports it. Contact
the Product Managers, Sharon Oneill (DELNI::ONEILL) and George Nielsen
(DELNI::G_NIELSEN) for info on the others (DEFAA, DEFQA, DEFTA, DEMFA,
and DEFZA).
>>
>> Q2. I heard several months ago that switch from FDDI to FDX is
>> done by setting MIB via SNMP. FDX to FDDI is done
>> automatically.
>> But FDX program summary says that both of FDDI <--> FDX are
>> done automatically. Which is correct ?
The firmware, driver, or host-based app (usually through SNMP) can turn
on or turn off FDXEnable. If it's not turned on, then on point-point
connections, the FW won't even try to enable FDX. If it IS turned on,
then on point-point connections where BOTH nodes have FDX enabled, FDX
operation will commence. There are additional MIB objects which
indicate the current FDX status. See the latest DEC private MIB for
details on these objects.
Just as an FYI, on the DEFEA we have FDXEnable shut off by default.
You need to explicitly enable it in the driver or app. This was done
intentionally.
- Larry
|