RE: [cisco-ttl] 4506 CPU problem

From: Serhat Uslay <serhat.uslay_at_....>
Date: Thu Dec 14 2006 - 01:42:41 EET

Cihan,
En fazla CPU kullanan process ler asagida. "sh platform health" herhalde eksikti , onu bana attachment olarak yollarmisin (sh config ile beraber) ? bunlar icinde CDP bana fazla gibi gozuktu. Gerekli olmadigi yerlerde cdp kaldir. Birde spanning tree loop olabilir. STP ye ihtiyacin olmadigi portlarda "portfast" kullanarak STP yi durdur.Eger bunlar hala problemi cozmezse CPU port sniffing yaparak CPU ya giden paketleri gormemiz gerekir. Bunun icin asagidaki dokumana bak. Ethereal ciktisi yollarsan CPU ya giden paketlere bakip fikrimi soyleyebilirim. http://www.cisco.com/en/US/customer/products/hw/switches/ps4324/products_configuration_guide_chapter09186a008019d0e7.html#1039942

13      334208   1144527        292  0.15%  0.14%  0.15%   0 ARP Input 
34     1718052    299630       5733  0.55%  0.60%  0.61%   0 IDB Work
  68      905292    480199       1885  2.23%  0.56%  0.42%   0 CDP 
Protocol
  73     2397620  12117760        197  0.79%  0.81%  0.79%   0 IP Input
  76     7380668   3884189       1900  2.95%  2.46%  2.46%   0 Spanning 

Tree

---

This email is intended for the named recipient only. It may contain information which is confidential, commercially sensitive, or copyright. If you are not the intended recipient you must not reproduce or distribute any part of the email, disclose its contents, or take any action in reliance. If you have received this email in error, please contact the sender and delete the message. It is your responsibility to scan this email and any attachments for viruses and other defects. To the extent permitted by law, Zurich and its associates will not be liable for any loss or damage arising in any way from this communication including any file attachments. We may monitor email you send to us, either as a reply to this email or any email you send to us, to confirm our systems are protected and for compliance with company policies. Although we take reasonable precautions to protect the confidentiality of our email systems, we do not warrant the confidentiality or security of email or attachments we receive.

[Non-text portions of this message have been removed] Received on Thu Dec 14 14:27:06 2006