| >If I connect thin wire ethernet to the BNC connector on the back of the
>stack director I can contact the stack with clearvisn. However if I
>connect the stack to the network via the AUI MM10 (and a BNC transceiver)
>it will not talk to clearvisn.
Sounds like the Slot 1 624T Port Group w/ AUI is not connected to the
Backplane TW. The Stack Director itself only talks to the backplane
on Backplane TW, not any of the other LAN's. Using Clearvisn attach
the Slot 1 Port Group containing the AUI to the Backplane TW.
1) View LAN Interconnect
2) Select Slot 1 624T
3) Click on Port Switch Button
4) Attach TW to Ports 13-24 & MM10 B
5) Back in the LAN Interconnect, pull down Slot 1
TW Pull Down thingie (the blue one) to the Backplane TW.
Alternatively, if Clearvisn is not possible, use the console port
on the Stack Director to do a Factory Reset of the 624T in Slot 1.
This forces both banks of ports into 1 port group and attaches that
port group to the Backplane TW. At this point the TW attached to the
AUI should be connected to the Stack Director through the Backplane TW
and so ClearVision should be able to do it's thing.
Be forewarned that this scheme of managing through the AUI MM10
has it's drawbacks. If for some reason the 624T in slot 1 fails
the management connection to the Stack will be lost. To avoid
this the Stack Director has it's own ports.
>If I connect thin wire ethernet to the BNC connector on the back of the
>stack director, the backplane activity lights go on all four modules, but
>if it is connected via the AUI MM10 only the bottom of the stack backplane
>led flashes with traffic.
This confirms my suspicion that the Slot 1 AUI MM10 is not
connected to the Backplane TW. It sounds like Slot 1 banks are
separated into 2 port groups, and Bank A is connected to the
Backplane TW and Bank B (with the AUI MM10) is not. When the
thin wire ethernet is attached to the Stack Director, I bet the
first of the 3 backplane activity lights goes on, indicating that
the Bank A has activity through the Backplane TW. But if the
thin wire ethernet is attached to the AUI MM10 then its the
middle of the 3 backplane activity lights which goes on,
indicating traffic on Bank B.
Sounds like some basic training in Clearvisn and the MS600
may be in order.
|
| I have just recoved the following mail from the customer.
None of this works I am afraid. I have tried both methods suggested to
no
avail. Please let me know exactly what info you require to fix this
problem. The MM10-B just will not connect to the thinwire - why?
As for you asking why management was necessary through the AUI port on
the front - the reason is because there is no AUI port on the stack
director back panel. A very silly omission. These repeaters are all
situated a long way apart and you have to use fibre.
Allow me to expand and describe the various settings that clearvisn
shows:
Lan interconnect shows four devices, device 1 (bottom of stack) has a
blue thingy pulled down to thinwire backplane - the thingy has a number 3
on it, all the other devices 2 to 4 have their blue thingys pulled down to
the thinwire, they have a number 4 on them. Theres also a green/brown
thingy for all the devices with the number 1 on it and they are not
pulled down to a backplane lan.
Pulling up the port switch dialog for device 1 shows that ports 13-24 and
MM10-B are connected to the thinwire.
Does the fact I have only one MM-10 installed make any difference?
There is a hole in the front of the repeater because no MM-10 blanking plate
was provided.
Any further input is appreciatted.
Steven F
|
|
With your stack configured as you've described it, it
ought to be working. I tested it out in the lab and it
worked just fine. I can't say why your's isn't. Here are
a few things to try out.
1) Make sure the Stack Director's TW is terminated correctly.
If there is no cable attached, put on a single terminator
(no T's).
2) Make sure the AUI MM10 is in port B, the right hand position.
Due to power limitations port A doesn't get the 12v needed
by AUI.
3) Remove and reinsert the MM10 and carrier card to make
sure all contacts are clean. Make sure the cards are inserted
fully and their screws torqued down tight.
4) Make sure the TW MAU attached to the MM10 actually works.
If possible test it our on another installation.
5) If the above fail, it may be a hardware failure. Try to
isolate the fault by swapping the carrier card/MM10 into
another 624T. It may be time to get field service involved.
(Maybe that's you!)
> Does the fact I have only one MM-10 installed make any difference?
It should work fine with only one MM10.
> There is a hole in the front of the repeater because no MM-10 blanking
> plate was provided.
Either a blanking plate or MM10 should have been installed
in the factory. To ensure proper airflow through the module,
please cover up the open hole. A bit of tape will suffice.
> As for you asking why management was necessary through the AUI port on
> the front - the reason is because there is no AUI port on the stack
> director back panel. A very silly omission.
This is supposedly a low cost system. For low cost
you don't get everything. I suppose it can be debated
whether the right things were included and the right things
left out. If the feature you need was left out, you will
undoubtedly believe the wrong choice was made. Sorry...
> These repeaters are all situated a long way apart and you have
> to use fibre.
As good a reason as I can think of.
|