On Thursday, 11/11/2004 at 08:26 CST, Harold Grovesteen <[EMAIL PROTECTED]> wrote: > 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).
I second this suggestion. As Harold notes, auto-negotiation across manufacturers or brands is a crap shoot, whether it's speed or duplex settings. And since IBM doesn't manufacture any of the switches these days ..... If it works, great. If not, oh well. Just add manual configuration to the problem determination checklist. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- 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
