Comments inline. > I have 4 6509 cats that are giving me problems. Congratulations on having four 6509s to play with. Sorry about the problems. For particular modules > on > the switch, user will not be able to login to network. I move them to > different module on same switch all works fine. I look at switch, port > status all is fine. When you say that the user will not be able to log into the network, are you also saying that each and every port on each of these modules are configured alike? For example, can I presume that these are access ports you are referencing, and as such all have received the "set port host" command? What indications are you getting of trouble. Can these hosts ping each other? Can they ping their default gateway? How far (if at all) can they get? Do they even get a link light? Have you attempted to fully reseat the modules in question, or swap them out with a different slot? I check logs on switch and I see for the ports > giving > me problem it reports "Coil Pinnacle Header Checksum Error". What the > hell > is this? I searched Cisco's site and find nothing. I can only infer about what it is, but my SWAG type guess would be some form of an ASIC, such as the SAINT, Phoenix, etc. Regarding the specific error, you may want to look at this link (watch wrap): http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/reln otes/78_6218.htm Search within the page for both "coil" and "pinnacle". Also read the note on reseating the modules from a pinnacle synch error. To wit: If you see minor hardware failures or Pinnacle sync errors on bootup, reconfirm that the supervisor engine and all the switching modules are fully seated, the ejector levers are fully depressed, and the thumbscrews are fully tightened. HTH, Paul Werner ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag _________________________________ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
