Dispatch Unit ASA is high

Dears, 
we have  ASA 5520 the CPU is high 
ASA5520# show processes cpu-usage sorted 
PC         Thread       5Sec     1Min     5Min   Process
081a86c4   6c1afa08    95.4%    95.1%    95.6%   Dispatch Unit
please help how I decrease CPU 
Any help to understand this is much appreciated.

show cpu
show processes cpu-usage
**This will tell us which process is consuming the most CPU.
**Dispatch Unit is the "packet processing" process of the ASA. If the Dispatch Unit is showing high utilization, take a packet capture (pcap) from the ASA and view it in Wireshark to see what traffic is causing the most load on the ASA.
thanks I solved the issue

Similar Messages

  • High CPU due to dispatch unit in cisco ASA 5540

    Hi Any suggestion help
    High CPU due to dispatch unit in cisco ASA 5540
    ciscoasa# sh processes cpu-usage
    PC         Thread       5Sec     1Min     5Min   Process
    0805520c   ad5afdf8     0.0%     0.0%     0.0%   block_diag
    081a8d34   ad5afa08    82.6%    82.1%    82.3%   Dispatch Unit
    083b6c05   ad5af618     0.0%     0.0%     0.0%   CF OIR
    08a60aa0   ad5af420     0.0%     0.0%     0.0%   lina_int
    08069f06   ad5aee38     0.0%     0.0%     0.0%   Reload Control Thread
    08072196   ad5aec40     0.0%     0.0%     0.0%   aaa
    08c76f3d   ad5aea48     0.0%     0.0%     0.0%   UserFromCert Thread
    080a6f36   ad5ae658     0.0%     0.0%     0.0%   CMGR Server Process
    080a7445   ad5ae460     0.0%     0.0%     0.0%   CMGR Timer Process
    081a815c   ad5ada88     0.0%     0.0%     0.0%   dbgtrace
    0844d75c   ad5ad2a8     0.0%     0.0%     0.0%   557mcfix
    0844d57e   ad5ad0b0     0.0%     0.0%     0.0%   557statspoll
    08c76f3d   ad5abef8     0.0%     0.0%     0.0%   netfs_thread_init
    09319755   ad5ab520     0.0%     0.0%     0.0%   Chunk Manager
    088e3f0e   ad5ab328     0.0%     0.0%     0.0%   PIX Garbage Collector
    088d72d4   ad5ab130     0.0%     0.0%     0.0%   IP Address Assign
    08ab1cd6   ad5aaf38     0.0%     0.0%     0.0%   QoS Support Module
    08953cbf   ad5aad40     0.0%     0.0%     0.0%   Client Update Task
    093698fa   ad5aab48     0.0%     0.0%     0.0%   Checkheaps
    08ab6205   ad5aa560     0.0%     0.0%     0.0%   Quack process
    08b0dd52   ad5aa368     0.0%     0.0%     0.0%   Session Manager
    08c227d5   ad5a9f78     0.0%     0.0%     0.0%   uauth
    08bbf615   ad5a9d80     0.0%     0.0%     0.0%   Uauth_Proxy
    08bf5cbe   ad5a9798     0.0%     0.0%     0.0%   SSL
    08c20766   ad5a95a0     0.0%     0.0%     0.0%   SMTP
    081c0b4a   ad5a93a8     0.0%     0.0%     0.0%   Logger
    08c19908   ad5a91b0     0.0%     0.0%     0.0%    Syslog Retry Thread
    08c1346e   ad5a8fb8     0.0%     0.0%     0.0%   Thread Logger
    08e47c82   ad5a81f0     0.0%     0.0%     0.0%   vpnlb_thread
    08f0f055   ad5a7a10     0.0%     0.0%     0.0%   pci_nt_bridge
    0827a43d   ad5a7620     0.0%     0.0%     0.0%   TLS Proxy Inspector
    08b279f3   ad5a7428     0.0%     0.0%     0.0%   emweb/cifs_timer
    086a0217   ad5a7230     0.0%     0.0%     0.0%   netfs_mount_handler
    08535408   ad5a7038     0.0%     0.0%     0.0%   arp_timer
    0853d18c   ad5a6e40     0.0%     0.0%     0.0%   arp_forward_thread
    085ad295   ad5a6c48     0.0%     0.0%     0.0%   Lic TMR
    08c257b1   ad5a6a50     0.0%     0.0%     0.0%   tcp_fast
    08c28910   ad5a6858     0.0%     0.0%     0.0%   tcp_slow
    08c53f79   ad5a6660     0.0%     0.0%     0.0%   udp_timer
    080fe008   ad5a6468     0.0%     0.0%     0.0%   CTCP Timer process
    08df6853   ad5a6270     0.0%     0.0%     0.0%   L2TP data daemon
    08df7623   ad5a6078     0.0%     0.0%     0.0%   L2TP mgmt daemon
    08de39b8   ad5a5e80     0.0%     0.0%     0.0%   ppp_timer_thread
    08e48157   ad5a5c88     0.0%     0.0%     0.0%   vpnlb_timer_thread
    081153ff   ad5a5a90     0.0%     0.0%     0.0%   IPsec message handler
    081296cc   ad5a5898     0.0%     0.0%     0.0%   CTM message handler
    089b2bd9   ad5a56a0     0.0%     0.0%     0.0%   NAT security-level reconfiguration
    08ae1ba8   ad5a54a8     0.0%     0.0%     0.0%   ICMP event handler
    I want exact troubleshooting.
    (1) Steps to follow.
    (2) Required configuration
    (3) Any good suggestions
    (4) Any Tool to troubleshoot.
    Suggestions are welcome

    Hello,
    NMS is probably not the right community to t/s this. You probably want to move this to Security group (Security > Firewalling).
    In the meanwhile, i have some details to share for you to check, though i am not a security/ASA expert.
    The Dispatch Unit is a process that continually runs on single-core ASAs (models 5505, 5510, 5520, 5540, 5550). The Dispatch Unit takes packets off of the interface driver and passes them to the ASA SoftNP for further processing; it also performs the reverse process.
    To determine if the Dispatch Unit process is utilizing the majority of the CPU time, use the command show cpu usage and show process cpu-usage sorted non-zero
    show cpu usage (and show cpu usage detail) will show the usage of the ASA CPU cores:
    ASA# show cpu usage
    CPU utilization for 5 seconds = 0%; 1 minute: 1%; 5 minutes: 0%
    show process cpu-usage sorted non-zero will display a sorted list of processes that are using the CPU usage. 
    In the example below, the Dispatch Unit process has used 50 percent of the CPU for the last 5 seconds:
    ASA# show process cpu-usage sorted non-zero
    0x0827e731 0xc85c5bf4 50.5% 50.4% 50.3% Dispatch Unit
    0x0888d0dc 0xc85b76b4 2.3% 5.3% 5.5% esw_stats
    0x090b0155 0xc859ae40 1.5% 0.4% 0.1% ssh
    0x0878d2de 0xc85b22c8 0.1% 0.1% 0.1% ARP Thread
    0x088c8ad5 0xc85b1268 0.1% 0.1% 0.1% MFIB
    0x08cdd5cc 0xc85b4fd0 0.1% 0.1% 0.1% update_cpu_usage
    If Dispatch Unit is listed as a top consumer of CPU usage, then use this document to narrow down what might be causing the Dispatch Unit process to be so active.
    Most cases of high CPU utilization occur because the Dispatch Unit process is high. Common causes of high utilization include:
    Oversubscription
    Routing loops
    Host with a high number of connections
    Excessive system logs
    Unequal traffic distribution
    More t/s details can be shared by the ASA members from the community.
    HTH
    -Thanks
    Vinod

  • Dispatch Unit - High CPU

    Hi All,
    I'm trying to do some research on the Dispatch Unit process.  It seems High CPU and this process go hand in hand.  I haven't figured out an effective way of determining what underlying issue is the actual source.  Can someone point me in the right direction to try an understand what the Dispatch Unit process is doing?  I have an ASA 5550.  I have seen the cpu hover around 85% +- 5% for sustained long periods, 30 - 60 min +.  I have always been under the impression that around 80% cpu and you're probably dropping packets (that could be an out-dated belief).
    Any help to understand this is much appreciated.
    -E

    Interface GigabitEthernet0/0 "Outside", is up, line protocol is up
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
            Input flow control is unsupported, output flow control is off
            MAC address 503d.e51e.ca06, MTU 1500
            IP address X.X.X.X, subnet mask 255.255.255.128
            533966821 packets input, 97651127709 bytes, 0 no buffer
            Received 281755 broadcasts, 0 runts, 0 giants
            0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
            0 pause input, 0 resume input
            0 L2 decode drops
            531835755 packets output, 523869066435 bytes, 254 underruns
            0 pause output, 0 resume output
            0 output errors, 0 collisions, 0 interface resets
            0 late collisions, 0 deferred
            0 input reset drops, 0 output reset drops, 0 tx hangs
            input queue (blocks free curr/low): hardware (255/230)
            output queue (blocks free curr/low): hardware (255/0)
      Traffic Statistics for "Outside":
            533805632 packets input, 87594789839 bytes
            531836009 packets output, 514115438627 bytes
            8499758 packets dropped
          1 minute input rate 3201 pkts/sec,  456343 bytes/sec
          1 minute output rate 3414 pkts/sec,  3194657 bytes/sec
          1 minute drop rate, 42 pkts/sec
          5 minute input rate 3192 pkts/sec,  462319 bytes/sec
          5 minute output rate 3347 pkts/sec,  3087920 bytes/sec
          5 minute drop rate, 44 pkts/sec
    Interface GigabitEthernet0/1 "", is up, line protocol is up
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
            Input flow control is unsupported, output flow control is off
            Available but not configured via nameif
            MAC address 503d.e51e.ca07, MTU not set
            IP address unassigned
            52743008732 packets input, 10981273483975 bytes, 0 no buffer
            Received 67316769 broadcasts, 0 runts, 0 giants
            227203 input errors, 0 CRC, 0 frame, 227203 overrun, 0 ignored, 0 abort
            0 pause input, 0 resume input
            0 L2 decode drops
            52646387186 packets output, 10004093219462 bytes, 59370 underruns
            0 pause output, 0 resume output
            0 output errors, 0 collisions, 2 interface resets
            0 late collisions, 0 deferred
            0 input reset drops, 0 output reset drops, 0 tx hangs
            input queue (blocks free curr/low): hardware (255/230)
            output queue (blocks free curr/low): hardware (253/0)
    Interface GigabitEthernet0/1.700 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 700
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            1484005458 packets input, 945109157423 bytes
            1549237026 packets output, 1000635823115 bytes
            8044767 packets dropped
    Interface GigabitEthernet0/1.702 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 702
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            8943750366 packets input, 2755931796297 bytes
            8526491966 packets output, 1914193676672 bytes
            6630966 packets dropped
    Interface GigabitEthernet0/1.704 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 704
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            7016462086 packets input, 1450478554512 bytes
            7065543596 packets output, 1479140251162 bytes
            2880196 packets dropped
    Interface GigabitEthernet0/1.706 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 706
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            64416266 packets input, 7923320970 bytes
            38348092 packets output, 36506546909 bytes
            17763881 packets dropped
    Interface GigabitEthernet0/1.708 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 708
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            499990620 packets input, 132317640462 bytes
            479568124 packets output, 94656034995 bytes
            5732396 packets dropped
    Interface GigabitEthernet0/1.710 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 710
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            456697118 packets input, 142353101507 bytes
            436063268 packets output, 77074679645 bytes
            2048852 packets dropped
    Interface GigabitEthernet0/1.712 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 712
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            4611219 packets input, 374277118 bytes
            3161754 packets output, 1164648244 bytes
            2043267 packets dropped
    Interface GigabitEthernet0/1.714 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 714
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            32096378 packets input, 4467537888 bytes
            27557898 packets output, 16522329528 bytes
            4961549 packets dropped
    Interface GigabitEthernet0/1.716 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 716
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            18831803 packets input, 8344011207 bytes
            22523531 packets output, 22066952655 bytes
            2861535 packets dropped
    Interface GigabitEthernet0/1.718 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 718
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            989577333 packets input, 649122513712 bytes
            1178962688 packets output, 379217574278 bytes
            467267 packets dropped
    Interface GigabitEthernet0/1.720 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 720
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            3 packets input, 126 bytes
            4 packets output, 112 bytes
            0 packets dropped
    Interface GigabitEthernet0/1.722 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 722
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            284902407 packets input, 36413839768 bytes
            388643668 packets output, 140011990801 bytes
            5724539 packets dropped
    Interface GigabitEthernet0/1.724 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 724
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            92120267 packets input, 80528735942 bytes
            97416524 packets output, 69199084337 bytes
            2229445 packets dropped
    Interface GigabitEthernet0/1.726 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 726
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            3 packets input, 126 bytes
            4 packets output, 112 bytes
            0 packets dropped
    Interface GigabitEthernet0/1.728 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 728
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            3 packets input, 126 bytes
            4 packets output, 112 bytes
            0 packets dropped
    Interface GigabitEthernet0/1.730 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 730
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            3068433 packets input, 570069307 bytes
            2561350 packets output, 693274747 bytes
            826890 packets dropped
    Interface GigabitEthernet0/1.732 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 732
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            8974460 packets input, 565390165 bytes
            32 packets output, 896 bytes
            8974413 packets dropped
    Interface GigabitEthernet0/1.734 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 734
            Description: xxxx
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.252.0
      Traffic Statistics for "xxxx":
            32835704482 packets input, 3603954525664 bytes
            32826034457 packets output, 3611196110356 bytes
            8986964 packets dropped
    Interface GigabitEthernet0/1.736 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 736
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.255.0
      Traffic Statistics for "xxxx":
            33 packets input, 1386 bytes
            33 packets output, 924 bytes
            0 packets dropped
    Interface GigabitEthernet0/1.737 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 737
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.255.0
      Traffic Statistics for "xxxx":
            1517009 packets input, 121262718 bytes
            751299 packets output, 325112414 bytes
            816845 packets dropped
    Interface GigabitEthernet0/1.738 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 738
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.255.0
      Traffic Statistics for "xxxx":
            5113485 packets input, 350891222 bytes
            3161353 packets output, 1932620453 bytes
            2453351 packets dropped
    Interface GigabitEthernet0/1.739 "xxxx", is up, line protocol is up
    # Attention: This interface is located in a PCI-e x23 slot. For #
    # optimal throughput, install the interface in a PCI-e x26 slot #
    # if one is available. Refer to 'show controller slot'.        #
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            VLAN identifier 739
            MAC address 503d.e51e.ca07, MTU 1500
            IP address xxxx, subnet mask 255.255.255.0
      Traffic Statistics for "xxxx":
            771783 packets input, 104804795 bytes
            431603 packets output, 305062467 bytes
            408596 packets dropped
    Interface GigabitEthernet0/2 "", is administratively down, line protocol is down
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            Auto-Duplex, Auto-Speed
            Input flow control is unsupported, output flow control is off
            Available but not configured via nameif
            MAC address 503d.e51e.ca08, MTU not set
            IP address unassigned
            0 packets input, 0 bytes, 0 no buffer
            Received 0 broadcasts, 0 runts, 0 giants
            0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
            0 pause input, 0 resume input
            0 L2 decode drops
            0 packets output, 0 bytes, 0 underruns
            0 pause output, 0 resume output
            0 output errors, 0 collisions, 2 interface resets
            0 late collisions, 0 deferred
            0 input reset drops, 0 output reset drops, 0 tx hangs
            input queue (blocks free curr/low): hardware (255/255)
            output queue (blocks free curr/low): hardware (255/255)
    Interface GigabitEthernet0/3 "Failover", is up, line protocol is up
      Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
            Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
            Input flow control is unsupported, output flow control is off
            Description: LAN/STATE Failover Interface
            MAC address 503d.e51e.ca09, MTU 1500
            IP address 10.255.255.1, subnet mask 255.255.255.252
            843173 packets input, 276753572 bytes, 0 no buffer
            Received 61 broadcasts, 0 runts, 0 giants
            0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
            0 pause input, 0 resume input
            0 L2 decode drops
            577776501 packets output, 687842224236 bytes, 0 underruns
            0 pause output, 0 resume output
            0 output errors, 0 collisions, 1 interface resets
            0 late collisions, 0 deferred
            18 input reset drops, 0 output reset drops, 0 tx hangs
            input queue (blocks free curr/low): hardware (255/230)
            output queue (blocks free curr/low): hardware (228/178)
      Traffic Statistics for "Failover":
            843037 packets input, 257733014 bytes
            577776358 packets output, 677442239604 bytes
            0 packets dropped
          1 minute input rate 1 pkts/sec,  127 bytes/sec
          1 minute output rate 1579 pkts/sec,  1852671 bytes/sec
          1 minute drop rate, 0 pkts/sec
          5 minute input rate 1 pkts/sec,  125 bytes/sec
          5 minute output rate 1575 pkts/sec,  1848475 bytes/sec
          5 minute drop rate, 0 pkts/sec
    Interface Management0/0 "management", is down, line protocol is down
      Hardware is i82557, BW 100 Mbps, DLY 100 usec
            Auto-Duplex, Auto-Speed
            Input flow control is unsupported, output flow control is unsupported
            MAC address 503d.e51e.ca05, MTU 1500
            IP address 192.168.1.1, subnet mask 255.255.255.0
            0 packets input, 0 bytes, 0 no buffer
            Received 0 broadcasts, 0 runts, 0 giants
            0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
            0 pause input, 0 resume input
            0 L2 decode drops
            0 packets output, 0 bytes, 0 underruns
            0 pause output, 0 resume output
            0 output errors, 0 collisions, 0 interface resets
            0 babbles, 0 late collisions, 0 deferred
            0 lost carrier, 0 no carrier
            0 input reset drops, 0 output reset drops
            input queue (curr/max packets): hardware (0/0) software (0/0)
            output queue (curr/max packets): hardware (0/0) software (0/0)
      Traffic Statistics for "management":
            0 packets input, 0 bytes
            0 packets output, 0 bytes
            0 packets dropped
          1 minute input rate 0 pkts/sec,  0 bytes/sec
          1 minute output rate 0 pkts/sec,  0 bytes/sec
          1 minute drop rate, 0 pkts/sec
          5 minute input rate 0 pkts/sec,  0 bytes/sec
          5 minute output rate 0 pkts/sec,  0 bytes/sec
          5 minute drop rate, 0 pkts/sec
            Management-only interface. Blocked 0 through-the-device packets
    Interface GigabitEthernet1/0 "", is administratively down, line protocol is down
      Hardware is VCS7380 rev01, BW 1000 Mbps, DLY 10 usec
            Auto-Duplex, Auto-Speed
            Input flow control is unsupported, output flow control is off
            Media-type configured as RJ45 connector
            Available but not configured via nameif
            MAC address 503d.e51e.ca1b, MTU not set
            IP address unassigned
            0 packets input, 0 bytes, 0 no buffer
            Received 0 broadcasts, 0 runts, 0 giants
            0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
            0 pause input, 0 resume input
            0 L2 decode drops
            0 packets output, 0 bytes, 0 underruns
            0 pause output, 0 resume output
            0 output errors, 0 collisions, 0 interface resets
            0 late collisions, 0 deferred
            0 rate limit drops
            0 input reset drops, 0 output reset drops
            input queue (blocks free curr/low): hardware (0/0)
            output queue (blocks free curr/low): hardware (0/0)
    Interface GigabitEthernet1/1 "", is administratively down, line protocol is down
      Hardware is VCS7380 rev01, BW 1000 Mbps, DLY 10 usec
            Auto-Duplex, Auto-Speed
            Input flow control is unsupported, output flow control is off
            Media-type configured as RJ45 connector
            Available but not configured via nameif
            MAC address 503d.e51e.ca1c, MTU not set
            IP address unassigned
            0 packets input, 0 bytes, 0 no buffer
            Received 0 broadcasts, 0 runts, 0 giants
            0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
            0 pause input, 0 resume input
            0 L2 decode drops
            0 packets output, 0 bytes, 0 underruns
            0 pause output, 0 resume output
            0 output errors, 0 collisions, 0 interface resets
            0 late collisions, 0 deferred
            0 rate limit drops
            0 input reset drops, 0 output reset drops
            input queue (blocks free curr/low): hardware (0/0)
            output queue (blocks free curr/low): hardware (0/0)
    Interface GigabitEthernet1/2 "", is administratively down, line protocol is down
      Hardware is VCS7380 rev01, BW 1000 Mbps, DLY 10 usec
            Auto-Duplex, Auto-Speed
            Input flow control is unsupported, output flow control is off
            Media-type configured as RJ45 connector
            Available but not configured via nameif
            MAC address 503d.e51e.ca1d, MTU not set
            IP address unassigned
            0 packets input, 0 bytes, 0 no buffer
            Received 0 broadcasts, 0 runts, 0 giants
            0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
            0 pause input, 0 resume input
            0 L2 decode drops
            0 packets output, 0 bytes, 0 underruns
            0 pause output, 0 resume output
            0 output errors, 0 collisions, 0 interface resets
            0 late collisions, 0 deferred
            0 rate limit drops
            0 input reset drops, 0 output reset drops
            input queue (blocks free curr/low): hardware (0/0)
            output queue (blocks free curr/low): hardware (0/0)
    Interface GigabitEthernet1/3 "", is administratively down, line protocol is down
      Hardware is VCS7380 rev01, BW 1000 Mbps, DLY 10 usec
            Auto-Duplex, Auto-Speed
            Input flow control is unsupported, output flow control is off
            Media-type configured as RJ45 connector
            Available but not configured via nameif
            MAC address 503d.e51e.ca1e, MTU not set
            IP address unassigned
            0 packets input, 0 bytes, 0 no buffer
            Received 0 broadcasts, 0 runts, 0 giants
            0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
            0 pause input, 0 resume input
            0 L2 decode drops
            0 packets output, 0 bytes, 0 underruns
            0 pause output, 0 resume output
            0 output errors, 0 collisions, 0 interface resets
            0 late collisions, 0 deferred
            0 rate limit drops
            0 input reset drops, 0 output reset drops
            input queue (blocks free curr/low): hardware (0/0)
            output queue (blocks free curr/low): hardware (0/0)

  • Dispatch Unit - High Cpu Usage

    Hi,
    ASA5510 8.2.5(50)
    The Dispatch unit process is contantly having high cpu usage for last 10 hours.
    Things checked:
    1. show proc cpu-usage
    2. show perf 
        It seems fine . Output attached
    3. Show interfaces for error
        No error, overruns, underrruns on interfaces
    4. show traffic 
        Total cumulative through put on approx 4 Mbps.
         drop rate max is 3 pkts /sec randomly and rare occurance on some interfaces
         5. Connections and Xlate seem normal.
             approx 1100.
          Counters were reset 1 hour before the data was collected.
    # sh cpu usage 
    CPU utilization for 5 seconds = 39%; 1 minute: 38%; 5 minutes: 44%
    # sh processes cpu-usage sorted 
    PC         Thread       5Sec     1Min     5Min   Process
    081aadc4   a79aff7c    35.7%    37.5%    42.5%   Dispatch Unit
    0853f89e   a79a0b68     0.4%     0.2%     0.2%   ARP Thread
    # show perfmon 
    PERFMON STATS:                     Current      Average
    Xlates                                0/s          0/s
    Connections                          21/s         32/s
    TCP Conns                            17/s         28/s
    UDP Conns                             1/s          1/s
    URL Access                            0/s          0/s
    URL Server Req                        0/s          0/s
    TCP Fixup                             0/s          0/s
    TCP Intercept Established Conns       0/s          0/s
    TCP Intercept Attempts                0/s          0/s
     sh interface e0/0 | inc overrun
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    fw01/act# sh interface e0/1 | inc overrun
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    # sh conn all
    1135 in use, 8777 most used
    # sh xlate count 
    112 in use, 265 most used
    # show asp drop frame 
      No route to host (no-route)                                                870
      Flow is denied by configured rule (acl-drop)                            103915
      First TCP packet not SYN (tcp-not-syn)                                    1317
      Bad TCP checksum (bad-tcp-cksum)                                             2
      TCP failed 3 way handshake (tcp-3whs-failed)                              6695
      TCP RST/FIN out of order (tcp-rstfin-ooo)                                 4025
      TCP packet SEQ past window (tcp-seq-past-win)                               13
      TCP Out-of-Order packet buffer full (tcp-buffer-full)                     1949
      TCP Out-of-Order packet buffer timeout (tcp-buffer-timeout)                600
      TCP RST/SYN in window (tcp-rst-syn-in-win)                                   5
      TCP dup of packet in Out-of-Order queue (tcp-dup-in-queue)                 617
      TCP packet failed PAWS test (tcp-paws-fail)                               1248
      IPSEC tunnel is down (ipsec-tun-down)                                        2
      Slowpath security checks failed (sp-security-failed)                      1699
      DNS Inspect id not matched (inspect-dns-id-not-matched)                      4
      FP L2 rule drop (l2_acl)                                                 15436
      Dropped pending packets in a closed socket (np-socket-closed)                2
    Please let us know what reason can be there for high cpu usage by Dispatch unit under current statistics?
    What else should be checked  to ensure cpu usage comes down?
    Regards,
    Gurjit Singh
    Network Engineer
    Spooster IT Services.

    Hi Gurjar,
    r u getting the below mentioned syslog messages?
    Flow is denied by configured rule (acl-drop)                            103915
    106023, 106100, 106004
    TCP Out-of-Order packet buffer full (tcp-buffer-full)                     1949
    TCP Out-of-Order packet buffer full:
    This counter is incremented and the packet is dropped when appliance receives an
    out-of-order TCP packet on a connection and there is no buffer space to store this packet.
    Typically TCP packets are put into order on connections that are inspected by the
    appliance or when packets are sent to SSM for inspection. There is a default queue size
    and when packets in excess of this default queue size are received they will be dropped.
    Recommendations:
    On ASA platforms the queue size could be increased using queue-limit configuration
    under tcp-map.
    Similarly you need to check many reasons for the asp drop logs that you have captured and you need to monitor how much it is increasing and the difference.......
    but 40 % CPU utilization is a okay kind of thing and you do not need to worry if that happens only during peak hours ans it is not increasing drastically more and more.
    http://www.cisco.com/c/en/us/td/docs/security/asa/asa82/command/reference/cmd_ref/s2.html#wp1435096
    Regards
    Karthik

  • ASA Dispatch UNIT percentage increasing

    HI,
    I have just noticed that my Cisco ASA 5510 cpu utilization increasing upto 30-35 % and when i issue sh processes cpu-usage, i have found dispatch unit occupied most of utilization.
    Kindly help in this regards.
    Regards,
    Arshad Ahmed

    Hey mohamed,
    go for
    show xlate count
    show conn
    show conn count
    show block
    show memory detail
    show processes cpu-usage
    show processes cpu-hog
    show processes memory
    show interface
    show traffic
    show mroute
    show local-host
    . you will get the reason. 

  • Shift One sub org unit to different higher level Org unit

    Dear All,
    I have requirement of shifting few Org units to different higher Org units, is it possible through PPOME, PPOSE (By drag and drop)or by any other transaction.
    the Org unit which we want to shift is having position and attched holders also...
    Reply awaited..
    Regards,
    Kumar

    Hi,
    Thanks for the reply, but one more Query if position(obviously some person must be attached with this position) is moved to another Org unit,
    somewhere we have to make changes like IT0001 for that Employee.
    Regards,
    Kumar

  • ASA 5520 High Availability

    I have two ASA 5520s.  One has an IDS card and one doesn't. This makes the high availability wizard fail.  Can I manually setup the high availability.  I don't really need two ASA-SSM-20s.  I just want to have one ASA in Standby mode.  Is this possible.  Anybody have a configuration similar to this?
    Thanks,
    Alex Pfeil                  

    Hi,
    Let me first say that I have not configure a Failover pair where the units dont have matching hardware. So I kind of wonder even if the ASA accepts the configurations, will the failover act normally.
    Usually if I configure basic configurations for some ASA Failover pair I first configure all the basic configurations on the ASA and make sure that each interface on the ASA has the "ip address x.x.x.1 255.255.255.0 standby x.x.x.2" configuration under the interfaces
    I then configure the existing ASA with a basic Failover configuration such as
    failover
    failover replication http
    failover lan unit primary
    failover lan interface failover Management0/0
    failover key
    failover link failover Management0/0
    failover interface ip failover 255.255.255.0 standby
    I then prepare a blank ASA and finally configure its Failover too
    failover
    failover replication http
    failover lan unit secondary
    failover lan interface failover Management0/0
    failover key
    failover link failover Management0/0
    failover interface ip failover 255.255.255.0 standby
    I will then attach the Secondary unit to the network and finally attach the Failover link between the ASAs and let the Primary unit replicate all the configurations to the Secondary unit.
    Naturally this is something that would probably be best done during a separate scheduled maintanance break along with configuration backups etc just to be on the safe side.
    - Jouni

  • Assign a Position in CRM to an Organization Unit at a higher level.

    Hi,
    While configuring the Organizational Management in CRM 5.1, I have copied the sales areas created in ECC to CRM.
    The resulting structure is a freely definable Org Unit at the top level called Sales Area (as is was created in ECC) and under that all the Sales Organizations are existing.
    I need to create positions for the Sales Organizations and assign employees to these positions created.
    As per our client requirement, I need to create the positions at the higher level (probably the Org unit level) and assign the employees to these positions created.
    The reason for doing this is that the same employees work across different Sales Orgs.
    Is it possible to create the positions at the highest level so that they can be inherited by the Sales Orgs defined below or do i need to create the positions and the employees separately for each Sales Org.
    I would appreciate if you could answer at the earliest. I need to complete the configuration at the earliest.
    warm regards,
    Rohan Bhate

    Hello,
    Try this SAP CRM: Webclient UI - Framework for this kind of question.
    Regards,
    Fred

  • HU03 going to short dump for handling unit which has higher level handling

    Hi,
    I am ABAPer, i working on issue, HU03 is gong to short dump. i dubug the t code and find out that particular handling unit has higher level handling unit. I checked another handling unit which won't had higher level handling unit, that time it's not giving dump.
    Note: in HU03 T CODE, function module V51P_HU_CONTENS is fetching values. when ever handling unit has higher level handling unit, it's not fetching further values.
    venkey

    Hi,
    Goto NACE transaction code , there you select the application area then  it will give you the list  of output types then select specific output click processing routines then you will see the program name and  script used.
    Or esle goto SPRO tcode then you can find the functional tab there also you can get the details.
    Thanks,
    Aditya

  • ASA 5550 High Availability Situation

    We have a couple of 5550's setup as an active/passive HA pair.  Recently one of the firewalls (standby) had a hardware issue and needed to be replaced.  Would it be easier/better to just restore the backup config from the defective appliance or should we just use the HA wizard in ASDM or cli to configure the new standby firewall?
    Thanks,
    PTH

    Just replace the firewall and put in the failover commands then plug in the failover interface on each ASA and you will be good to go. The standby will download the active configuration.

  • GETVPN - Rekey High CPU

    Hi everybody.
    I got GETVPN infrastructure, with two keyservers and 32 group members.
    Every time the rekey process takes place, all the groupmembers present high cpu usage and the Crypto ACL consumes all of my resources.
    I am very lost, because is a pretty straight forward configuration.
    ROUTER# show process cpu history
    ROUTER 10:49:38 AM Tuesday Sep 30 2014 UTC
    9999999999999999444441111111111 11111 11111111111111
    999999999999999988888222223333399999333339999922222666662222
    100 ****************
    90 ****************
    80 ****************
    70 ****************
    60 ****************
    50 *********************
    40 *********************
    30 *********************
    20 ********************* *****
    10 ************************************************************
    0....5....1....1....2....2....3....3....4....4....5....5....6
    0 5 0 5 0 5 0 5 0 5 0
    CPU% per second (last 60 seconds)
    121111121112111112121212221112111111122211121111111111112212
    817295705770864893417188157650667447520279707886569543861074
    100
    90
    80
    70
    60
    50
    40
    30 * *
    20 *** ********** **# #***#*#***#*** ****#*#********** ***#*#
    10 ############################################################
    0....5....1....1....2....2....3....3....4....4....5....5....6
    0 5 0 5 0 5 0 5 0 5 0
    CPU% per minute (last 60 minutes)
    * = maximum CPU% # = average CPU%
    929 9 9 9 99 9 929299192939199 9 9 99 9 9 9 99 9 9 9 99 919 9 99 919 9 9
    939994959599798929199496919099595949949595949959496949949495949989099999
    100 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
    90 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
    80 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
    70 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
    60 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
    50 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
    40 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
    30 * * * * * ** * * * ** ***** ** * * ** * * * ** * * * ** * * * ** * * * *
    20 #** * * * ** * ****** ***#* ** * * ** * * * ** * * * ** * * * ** * * * *
    10 ##*** **********###########******* ** ***** **** *** ** ***** **********
    0....5....1....1....2....2....3....3....4....4....5....5....6....6....7..
    0 5 0 5 0 5 0 5 0 5 0 5 0
    CPU% per hour (last 72 hours)
    * = maximum CPU% # = average CPU%
    ROUTER#show process cpu sorted | e 0.00%
    CPU utilization for five seconds: 99%/23%; one minute: 39%; five minutes: 19%
    PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
    251 1298116 6286 206509 74.91% 22.56% 5.21% 0 Crypto ACL
    325 33652 32198 1045 0.23% 0.37% 0.43% 514 Virtual Exec
    2 4428 84728 52 0.15% 0.06% 0.07% 0 Load Meter
    119 356324 613777 580 0.15% 0.25% 0.27% 0 IP Input
    41 10124 423671 23 0.07% 0.08% 0.07% 0 Per-Second Jobs
    151 18788 601822 31 0.07% 0.18% 0.22% 0 CEF: IPv4 proces
    ROUTER#
    Keyserver conf:
    crypto isakmp policy 100
     encr aes
     hash md5
     authentication pre-share
     group 2
    crypto isakmp key cisco address 0.0.0.0
    crypto ipsec transform-set CRYPTO_AES esp-aes esp-sha-hmac 
    crypto ipsec profile PHASE-II
     set security-association lifetime seconds 7200
     set transform-set CRYPTO_AES 
    crypto gdoi group GETVPN_CLIENT
     identity number 7
     server local
      rekey lifetime seconds 43200
      rekey retransmit 10 number 2
      rekey authentication mypubkey rsa REKEY_CLIENT
      rekey transport unicast
      sa ipsec 1
       profile PHASE-II
       match address ipv4 ACL
       no replay
      address ipv4 10.1.1.176
      redundancy
       local priority 10
       peer address ipv4 10.1.1.176
    Thanks for your advice

    Hello,
    NMS is probably not the right community to t/s this. You probably want to move this to Security group (Security > Firewalling).
    In the meanwhile, i have some details to share for you to check, though i am not a security/ASA expert.
    The Dispatch Unit is a process that continually runs on single-core ASAs (models 5505, 5510, 5520, 5540, 5550). The Dispatch Unit takes packets off of the interface driver and passes them to the ASA SoftNP for further processing; it also performs the reverse process.
    To determine if the Dispatch Unit process is utilizing the majority of the CPU time, use the command show cpu usage and show process cpu-usage sorted non-zero
    show cpu usage (and show cpu usage detail) will show the usage of the ASA CPU cores:
    ASA# show cpu usage
    CPU utilization for 5 seconds = 0%; 1 minute: 1%; 5 minutes: 0%
    show process cpu-usage sorted non-zero will display a sorted list of processes that are using the CPU usage. 
    In the example below, the Dispatch Unit process has used 50 percent of the CPU for the last 5 seconds:
    ASA# show process cpu-usage sorted non-zero
    0x0827e731 0xc85c5bf4 50.5% 50.4% 50.3% Dispatch Unit
    0x0888d0dc 0xc85b76b4 2.3% 5.3% 5.5% esw_stats
    0x090b0155 0xc859ae40 1.5% 0.4% 0.1% ssh
    0x0878d2de 0xc85b22c8 0.1% 0.1% 0.1% ARP Thread
    0x088c8ad5 0xc85b1268 0.1% 0.1% 0.1% MFIB
    0x08cdd5cc 0xc85b4fd0 0.1% 0.1% 0.1% update_cpu_usage
    If Dispatch Unit is listed as a top consumer of CPU usage, then use this document to narrow down what might be causing the Dispatch Unit process to be so active.
    Most cases of high CPU utilization occur because the Dispatch Unit process is high. Common causes of high utilization include:
    Oversubscription
    Routing loops
    Host with a high number of connections
    Excessive system logs
    Unequal traffic distribution
    More t/s details can be shared by the ASA members from the community.
    HTH
    -Thanks
    Vinod

  • Asa high cpu

    I am seeing high cpu utilization on 5520.
    Any pointers on how to troubleshoot?
    fw# sh processes cpu-usage sorted non-zero
    PC         Thread       5Sec     1Min     5Min   Process
    0x081e1e11   0x6ddc1528   70.6%   66.5%   66.0%   Dispatch Unit
    0x08ed170c   0x6ddb9b48     1.6%     1.7%     1.8%   Logger
    0x08dd5f2c   0x6ddafee0     1.5%     1.5%     1.5%   SNMP Notify Thread
    0x08e8d045   0x6dd99348     0.1%     0.1%     0.1%   ssh

    Hello Kashish,
    Can you check how many connections and translations are there in ASA
    show conn count
    show xlate count
    also try to do a clear conn and clear xlate and see whether the CPU is coming down
    regards
    Harish.

  • ASA 5520 CPU High

    Dear Team,
    My asa utilization is showing 90%
    ASA image : asa804-k8.bin
    Please find the below output.
    # sh processes cpu-hog
    Process:      Dispatch Unit, PROC_PC_TOTAL: 1557, MAXHOG: 48, LASTHOG: 3
    LASTHOG At:   11:27:29 GMT Jul 13 2013
    PC:           8172a27 (suspend)
    Process:      Dispatch Unit, NUMHOG: 165, MAXHOG: 48, LASTHOG: 3
    LASTHOG At:   11:27:29 GMT Jul 13 2013
    PC:           8172a27 (suspend)
    Traceback:    8172a27  805e983
    # sh processes
      PC       SP       STATE       Runtime    SBASE     Stack Process
    Lwe 08051bac 6a90c32c 09b7aeb4          0 6a90a418 7920/8192 block_diag
    Mrd 08172a27 6a93cccc 09b7a7fc   23078782 6a91ce58 125548/131072 Dispatch Unit
    # sh service-policy global
    Global policy:
      Service-policy: global_policy
        Class-map: inspection_default
          Inspect: dns migrated_dns_map_1, packet 186139714, drop 25307, reset-drop 0
          Inspect: ftp, packet 9106, drop 0, reset-drop 8
          Inspect: h323 h225 _default_h323_map, packet 0, drop 0, reset-drop 0
          Inspect: h323 ras _default_h323_map, packet 0, drop 0, reset-drop 0
          Inspect: rsh, packet 0, drop 0, reset-drop 0
          Inspect: rtsp, packet 0, drop 0, reset-drop 0
          Inspect: esmtp _default_esmtp_map, packet 14599416, drop 5701, reset-drop 0
          Inspect: skinny , packet 0, drop 0, reset-drop 0
          Inspect: sunrpc, packet 0, drop 0, reset-drop 0
          Inspect: xdmcp, packet 0, drop 0, reset-drop 0
          Inspect: sip , packet 0, drop 0, reset-drop 0
          Inspect: netbios, packet 11549, drop 0, reset-drop 0
    Thanks in advance...

    Have you tried the steps suggested in Cisco's tech note here?

  • What does the 'rtcli async executor process' process do on a Cisco ASA and why would it cause high CPU load?

    I noticed that the CPU on our ASA had jumped from around %4 to 30% consistently a few weeks back.  The process below seems to be causing the load, but I can't find any information on what it does and how to resolve the issue.
    ASA# sh proc cpu-usage sorted non-zero
    PC         Thread       5Sec     1Min     5Min   Process
    0x08a24505   0x1bdb0124    25.4%    25.6%    25.6%   rtcli async executor process
    0x081ecc51   0x1bdc0f3c     4.7%     4.3%     4.1%   Dispatch Unit
    0x08e4687c   0x1bdc0528     0.3%     0.3%     0.3%   ssm4ge_cfg_poll_thread
    0x08a496d0   0x1bdbecf8     0.1%     0.1%     0.1%   Unicorn Admin Handler
    0x0866d56e   0x1bdafd1c     0.1%     0.1%     0.1%   ARP Thread
    A little more background that has me concerned is that I have the exact time when the jump occurred.  Since that time, I've lost ssh access to the ASA and can only access it via Telnet internally or the ASDM.  I checked the certificates and a new one was generated exactly when the spike occurred.  I am unsure wether or not that was a system triggered certificate generation, or if I have a security issue I need to address.  Heartbleed maybe??  
    Any insight would be greatly appreciated.

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    Sorry I wasn't clear, but when I was asking about "not a lot of traffic", I was wondering about actual  volume passing through the 2811.
    When I asked about "kind of tunnels", I was wondering about how they are configured.  E.g. GRE or IPSec/GRE or VTI, encryption options, other tunnel interface options.
    Perhaps the easiest way to check for fragmentation, is packet analyze the traffic passing through the 2811.

  • Can I override high-units with a  'system-property' attribute?

    In an attempt to centralize property configurations, can I override the high-units with a system-override?
    <backing-map-scheme>
    <read-write-backing-map-scheme>
    <internal-cache-scheme>
    <local-scheme>
    *<high-units system-property="high.for.prod">2G</high-units>*
    <unit-calculator>BINARY</unit-calculator>
    <expiry-delay>0</expiry-delay>
    </local-scheme>
    </internal-cache-scheme>

    You should be able to bu the correct syntax is...
    <high-units system-property="high.for.prod">2G</high-units>...without the underscores
    JK

Maybe you are looking for

  • My iphone 5 won't charge :(

    My iphone 5 won't charge with the cable I bought, I don't know if its because maybe it isn't an apple product? Can somone please help me! thank you

  • How to know that if an item/lot # combination is produced in an ORG?

    Hi All, I need to use this in a custom process which will manipulate the transactions in AR_INTERFACE TABLE before auto invoice process is ran. But my question is how can we know that an item is manufactured in a particular oraganization. Here is the

  • Error V1 322 u2013 Delete Reason for rejection

    Hi, I have the following error when I trying to delete the reason for rejection in sales order position: Error in building the index of the table XMVERF_POS / 0000396002 / 000010 Number message V1322 Internal Error Where 0000396002 is the sale order

  • JDEVELOPER  IDE SUCKS

    i only wish oracle corp is on the way to develop an IDE like the studio creator which uses simple style sheet concepts. I WASTE MOST OF THE TIME TO DEVELOP THE PRESENTATION LAYER THAN TO CONCENTRATE ON MY EXPERTISE(Business logic). I AM REALLY DISAPP

  • Oracle block corresponding to a given rowid.

    Hi all, When we know the rowid R of a row in a table named TABLE_TEST, how can we know the ID of the Oracle block containing this row? Thanks.