This is a physical layer issue so not a spanning tree issue which
requires a running link connection to function at the link layer.
Before going down the firmware release level path, ensure that any
auto-negotiation of duplex and speed is disabled on both sides of the
connection and manually configured the same speed and duplex on the OSA
and switch.  Make no assumptions.  Explicitly disable and configure.  If
any administrative tool allows these settings to be queried or trace
events can be generated that can provide additional information about
what the firmware thinks is going on can provide insight.  Problems with
auto-negotiation are very common in these situations (between products
from the same vendor let alone different vendors) and should be
eliminated from the picture first.  Even if it works in one setting
(host configuration) it may not in the other (trunk configuration).

Harold Grovesteen

David Boyes wrote:

First thing to check is the Alcatel firmware release level. Several
recent releases had serious problems with 802.1p trunk definitions.

Second, check the spanning tree resolution timeouts. Multiple VLANs on a
single port is a pathological case for spanning tree design if it's
implemented certain ways.

The link behavior makes me think it's a firmware thing. Something is
really unhappy in the software there.




We're having more adventures setting up VSWITCHes. Our OSA-E's are
configured 100Mb full duplex. Switches we're tried are
Alcaltel 6624 and
Alcatel 7700. Symptoms are the same - if the Alcatel switch port is
configured as a trunk at full duplex, we can't get a link
light. If the
switch is half duplex we get the link light but can't talk
through. If the
switch port is defined as a normal "host" port at full
duplex, the link
light comes on and we can connect Linux guests to the outside
(only on the
VLAN specified on the switch for that port, of course).

This seems to be extraordinarily odd behaviour at the physical layer,
occurring whether we have the OSA attached to the VSWITCH or
anything else.



---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390




---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to