Re: [cisco-ttl] merhaba

From: ali yorulmaz <blue49_49_at_....>
Date: Mon, 19 Nov 2007 01:00:39 -0800 (PST)


arkadaşlar teşekkürler ama sorun hala devam ediyor. aşağıda proceses ler içinde gördüğüm bir çıktıyı daha gönderiyorum    

  Process 35: TTY Background, state: Waiting for Event   Watching boolean 'tty_wakeup' (0x45AE115C), id 0x0, value False.   Watching a delta timer. Expires in 00:00:00.   1 waiting messages.        

  PID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process 
  35       12192  26755758          0  0.00%  0.00%  0.00%   0 TTY Background   
   
   
   
  Master6509#sh processes mem | i TTY
 PID TTY  Allocated      Freed    Holding    Getbufs    Retbufs Process
  35   0        744      19040      10024          0          0 TTY Background  
   
   
   
   
   
   

  Ayrıca sh version çıktısıda burda..    

  Cisco Internetwork Operating System Software IOS (tm) s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXE3, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2005 by cisco Systems, Inc. Compiled Tue 16-Aug-05 18:56 by kellmill Image text-base: 0x40021040, data-base: 0x42B08000   ROM: System Bootstrap, Version 12.2(17r)S2, RELEASE SOFTWARE (fc1) BOOTLDR: s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXE3, RELEASE SOFTWARE (fc1)   Master6509 uptime is 44 weeks, 1 day, 18 hours, 38 minutes Time since Master6509 switched to active is 44 weeks, 1 day, 18 hours, 40 minutes System returned to ROM by unknown reload cause - suspect boot_data[BOOT_COUNT] 0x0, BOOT_COUNT 0, BOOTDATA 19 (SP by power-on) System restarted at 16:18:31 EET Sat Jan 13 2007 System image file is "disk0:s72033-ipservicesk9_wan-mz.122-18.SXE3.bin"   

This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable

to comply with U.S. and local laws, return this product immediately.
  A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
  If you require further assistance please contact us by sending email to export_at_cisco.com.
  cisco WS-C6509-E (R7000) processor (revision 1.2) with 458720K/65536K bytes of memory. Processor board ID SMG0946N2DL
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache Last reset from power-on
SuperLAT software (copyright 1990 by Meridian Technology Corp). X.25 software, Version 3.0.0.
Bridging software.
TN3270 Emulation software.
3 Virtual Ethernet/IEEE 802.3 interfaces 158 Gigabit Ethernet/IEEE 802.3 interfaces 1917K bytes of non-volatile configuration memory. 8192K bytes of packet buffer memory.
  65536K bytes of Flash internal SIMM (Sector size 512K). Configuration register is 0x2102                       

serhat aslan <serhataslan22_at_yahoo.com> wrote:           

Bu tur bir hata protokolle ait bir hata degil, bu hata switch yazilimini yapan kisilerin durum analizi olarak kendi koyduklari bilgi hatalarina benziyor. O yuzden bu kisimlar mumkunse direk yada indirek ureticiye direk sorulmasi gerekiyor. Bahsi gecen seviye "3.derece hatalari" normalde onemli bir derece. Burda ise benim anladigim hardware yazilim bugina yada eksik kaynak kullanimina isaret ediyor. Sistem muhtemel schedule islemi icin belli bir cpu/ram kullanacaktir anormal durumlarda memory-leak durumlarinda ise cok krik hataya sebep olucaktir(sistem cakilmasi diyelim) ama burdaki hata bi tur bug degilde sanki sistem eksikligi durumunda urettigi bir tur hata/bilgi koduna benziyor. Sorunu uretici ile degil kendiniz cozmek istiyorsaniz(tafsiye edilmeyen metod) sistem kaynaklarinin kullanimini ve cpu/ram/interface istatisliklerinin durumlarini detayli kontrol ederek daha cok sistem kaynagini bosa cikarin mumkunse kullanabildiginiz en basit IOS'u yukleyin.

kolay gelsin,
Serhat Aslan

kaynak:

link:http://www.cisco.com/warp/public/63/scheduler_12422.html

ozetle: "These messages are not always caused by a software bug. They may be issued in response to either instantaneous or sustained demand on the router. Increased or persistent messages may indicate that the traffic load needs to be reviewed"

genis:

SCHED-3-THRASHING This message means that the indicated process has relinquished control 50 consecutive times and there are still outstanding events to be processed.

The following messages on the console indicate such a problem:

%SCHED-3-THRASHING: Process thrashing on watched queue 'ARP queue' (count 54).
-Process= "ARP Input", ipl= 5, pid= 6
-Traceback= 6020589C 60205BC4 60236520 601F4FD8 601F4FC4

These thrashing checks are intended to determine if a process is, for some reason, not doing its job. The thrashing check on watched queues (which is the troublesome message which is signaling) checks the number of elements on the queue. If this number remains the same for a given number of schedulings, the message is printed.

Unfortunately, some queues are length-limited, meaning that if the router gets very busy, the queues always stay at the maximum. As a result, the thrashing code in the scheduler gets confused and thinks that these queues have not been handled. The thrashing code has determined that the process which was supposed to handle the queue was not doing its job and prints the thrashing message.

The scheduler has been changed in later Cisco IOS software code. To keep track of whether the queues have been changed (so it can better determine whether or not the process is thrashing), the scheduler now notes whenever an item is removed from the queue, and only prints the thrashing message if nothing gets removed for a while.

Most of the time, the queue thrashing message is simply cosmetic.

These messages are not always caused by a software bug. They may be issued in response to either instantaneous or sustained demand on the router. Increased or persistent messages may indicate that the traffic load needs to be reviewed.

Note: These code changes are reported under CSCdj68470. If you are a registered user, you may use the Bug Toolkit to watch this bugID.

ali yorulmaz <blue49_49_at_yahoo.com> wrote: kendi sorunuma kendim çözüm bulayım.

The following error messages might appear on the console and in the log:

%SCHED-3-THRASHING: Process thrashing on watched message event.

-Process= "TTY Background", ipl= 6, pid= 20

-Traceback= 801BA4D4 801BA798 80114D94 801CEF34

This message indicates a situation that does not appear to affect any system service. The system generates these log messages when you enter the terminal monitor command and encounter excessive SSH traffic (such as debug messages). This problem is resolved in Release 12.2(18)SXF. (CSCdy80670)

ali yorulmaz <blue49_49_at_yahoo.com> wrote: Arkadaşlar merhaba

cisco catalyst 6500 şaselerde

Nov 7 09:13:42.427: %SCHED-3-THRASHING: Process thrashing on watched message event.
-Process= "TTY Background", ipl= 5, pid= 35
-Traceback= 40EAE80C 40EAEA84 40361154

şeklinde bir hata alıyorum
daha önce bir arkadaş daha yazmış aynı hatayı ancak kimse cevap yazamamış. ben araştırdım aşırı ssh bağlantısı olduğunda böyle bir hata oluşur demiş cisco. Tehlikeli değil demiş. Ama yine de ben bu hatayı kaldırmak istiyorum bir çözümü olan varsa sevinirim..



Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

[Non-text portions of this message have been removed]



Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.

[Non-text portions of this message have been removed]



Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.

[Non-text portions of this message have been removed]                                  



Get easy, one-click access to your favorites. Make Yahoo! your homepage.

[Non-text portions of this message have been removed] Received on Tue Nov 20 2007 - 11:46:20 CET

This archive was generated by hypermail 2.2.0 : Tue Nov 20 2007 - 11:46:23 CET