| Okay we'll try to shed some light...
>In a stack, Ethernet ports can be grouped and assigned to any of
>seven Ethernet LANs (implemented using the riser cards).
Yup - though a set of ports must be treated as a block. For example,
in the 624T, ports 1-12 are one group and 13-24 are another group.
These two groups can be put on separate LANs or all together on the
same LAN. The Thinwire connection can be associated with either group
or left alone.
>In a DEChub 900, the 600 series modules get power but no backplane
>connectivity. I presume that ports can still be grouped, and then connected to
>a LAN using a front-panel connection. Are there any restrictions in the number
>of groups that can be formed?
There is backplane connectivity in the hub! Just not as much as you want.
600 modules in the hub can connect to the TW channel and to the IMB0 channel,
so you can have Thinwire and 1 LAN connection. The other IMB channels are not
available because they reside on the lower connector, which 600 modules don't use.
(The stack uses the same 40-pin upper connector more efficiently, getting 1 TW
and 6 LANs, by subdividing IMB0 into 3 LANs and by using the signals that the
hub has to reserve for token ring to get 3 more LANs.)
>If two uplinks are installed in the 624EX, 12 ports can be assigned to one and
>12 to the other. Are permutations thereof allowed?
No. Each block of 12 travels as one unit.
>What happened to the 32-port PORTswitch that was meant to appear at the same
>time as the VNswitches? Am I missing something?
Yeah - the PORTswitch, and so are we. (It'll be along sometime.)
Dotsie
|