🚀 go-pugleaf

John, it dosn't seem that you can do much more. A trace on the ring from start
to finish of claim process will surely tell something, but you get filled up
buffer before the process is ended. May be if you start logging toward the
end of the claim process may tell you a clue. The fact that you saw claim and
then beaconing process started may have been caused by either a defective
cable which should cause more than one machine to beacon or the defective IBM
host thought there was a cable problem, a buggy host.

Take a  look at the cisco fddi interface (show int fddi 0): look for
bursts of carrier transitions when the IBM host is not functional. Turn debug
fddi-cmt on the upstream and downstream ciscoes from the IBM host if any and
monitor the fddi ring activity. I doubt you would see much, yet it may
suppliment your claim to IBM.


Good Luck!

Alex Bahoor
Customer Engineering
cisco Systems Inc
Mountain View CA 94043