High CPU Utilization on PIX-535

Hi All,
We are using Pix 535 as an external FW in our network and we are expiriencing high CPU utilization. The CPU is jumping to 60%-70% every 60 min.
I am using Cacti to monitor all the interfaces and we don't have a huge traffic that interface. Also I could not see any corolation between the traffic and the CPU graph. See below the screenshut of the CPU from Cacti:
Yesterday I changeed the perfmon setting to 3000000 and the CPU dropped down to 26%-30% for around 2hr and then it us started again to jump every 60min.
We are about to replace our Pix but in the meantime we are suffering from disconnetion , and slowness in our network.
Anybody has this issue?
See below our sh ver results :
Cisco PIX Security Appliance Software Version 7.2(4)
Compiled on Sun 06-Apr-08 13:39 by builders
System image file is "flash:/pix724.bin"
Config file at boot was "startup-config"
HERZLIA-PERIMETER-PIX up 85 days 0 hours
failover cluster up 3 years 53 days
Hardware:   PIX-535, 1024 MB RAM, CPU Pentium III 1000 MHz
Flash i28F640J5 @ 0x300, 16MB
BIOS Flash DA28F320J5 @ 0xfffd8000, 128KB
Encryption hardware device : VAC+ (Crypto5823 revision 0x1)
0: Ext: Ethernet0           : address is 000d.88ff.6048, irq 12
1: Ext: Ethernet1           : address is 000d.88ff.6049, irq 12
2: Ext: Ethernet2           : address is 000d.88ff.604a, irq 12
3: Ext: Ethernet3           : address is 000d.88ff.604b, irq 12
4: Ext: GigabitEthernet0    : address is 000e.0c05.92eb, irq 255
5: Ext: GigabitEthernet1    : address is 000e.0c05.022f, irq 11
6: Ext: GigabitEthernet2    : address is 000e.0c9e.cdd9, irq 11
7: Ext: GigabitEthernet3    : address is 000e.0c80.b859, irq 255
8: Ext: Ethernet4           : address is 000e.0c5d.8a26, irq 12
9: Ext: Ethernet5           : address is 000e.0c5d.88c1, irq 11
Licensed features for this platform:
Maximum Physical Interfaces : 14       
Maximum VLANs               : 150      
Inside Hosts                : Unlimited
Failover                    : Active/Active
VPN-DES                     : Enabled  
VPN-3DES-AES                : Enabled  
Cut-through Proxy           : Enabled  
Guards                      : Enabled  
URL Filtering               : Enabled  
Security Contexts           : 2        
GTP/GPRS                    : Disabled 
VPN Peers                   : Unlimited
This platform has an Unrestricted (UR) license.
Serial Number: 807030476
Running Activation Key: 0x110d483c 0x01751906 0x926d4e00 0x7537b580
Configuration last modified by enable_15 at 11:09:07.833 Jer Fri Oct 18 2013
Thanks,
Reuven

Hi Naveen,
Thanks a lot , this is realy urgent . See all that you requered :
CPU utilization for 5 seconds = 68%; 1 minute: 59%; 5 minutes: 37%
sh traffic
outside:
        received (in 3067903.354 secs):
                19582623703 packets     14005577988705 bytes
                6000 pkts/sec   4565000 bytes/sec
        transmitted (in 3067903.354 secs):
                15714123294 packets     5660650486747 bytes
                5000 pkts/sec   1845001 bytes/sec
      1 minute input rate 3186 pkts/sec,  1500299 bytes/sec
      1 minute output rate 2270 pkts/sec,  480558 bytes/sec
      1 minute drop rate, 17 pkts/sec
      5 minute input rate 2243 pkts/sec,  1421226 bytes/sec
      5 minute output rate 1925 pkts/sec,  551741 bytes/sec
      5 minute drop rate, 17 pkts/sec
Dirty-DMZ-SW-Vlan-55:
        received (in 3068362.914 secs):
                4057865661 packets      2042268645925 bytes
                1000 pkts/sec   665001 bytes/sec
        transmitted (in 3068362.914 secs):
                3264602039 packets      1011683053210 bytes
                1000 pkts/sec   329000 bytes/sec
      1 minute input rate 4 pkts/sec,  383 bytes/sec
      1 minute output rate 3 pkts/sec,  2354 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 3 pkts/sec,  366 bytes/sec
      5 minute output rate 2 pkts/sec,  1406 bytes/sec
      5 minute drop rate, 0 pkts/sec
DMZ-SW-Vlan-56:
        received (in 3068362.924 secs):
                2141967428 packets      1428493311756 bytes
                1 pkts/sec      465001 bytes/sec
        transmitted (in 3068362.924 secs):
                1957313765 packets      885033589235 bytes
                1 pkts/sec      288000 bytes/sec
      1 minute input rate 162 pkts/sec,  65294 bytes/sec
      1 minute output rate 151 pkts/sec,  44117 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 198 pkts/sec,  83495 bytes/sec
      5 minute output rate 182 pkts/sec,  69827 bytes/sec
      5 minute drop rate, 0 pkts/sec
Ewa-DMZ-Test-Sw-Vlan-57:
        received (in 3068362.934 secs):
                1477484 packets 94632104 bytes
                0 pkts/sec      0 bytes/sec
        transmitted (in 3068362.934 secs):
                1534775 packets 99159192 bytes
                0 pkts/sec      0 bytes/sec
      1 minute input rate 0 pkts/sec,  12 bytes/sec
      1 minute output rate 0 pkts/sec,  14 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 0 pkts/sec,  12 bytes/sec
      5 minute output rate 0 pkts/sec,  13 bytes/sec
      5 minute drop rate, 0 pkts/sec
Ewa-DMZ-Dev-Sw-Vlan-58:
        received (in 3068365.114 secs):
                509028966 packets       144181736547 bytes
                0 pkts/sec      46000 bytes/sec
        transmitted (in 3068365.114 secs):
                655383171 packets       573008234209 bytes
                0 pkts/sec      186001 bytes/sec
      1 minute input rate 68 pkts/sec,  9432 bytes/sec
      1 minute output rate 91 pkts/sec,  83192 bytes/sec
      1 minute drop rate, 6 pkts/sec
      5 minute input rate 62 pkts/sec,  9323 bytes/sec
      5 minute output rate 82 pkts/sec,  70495 bytes/sec
      5 minute drop rate, 7 pkts/sec
Ewa-Dmz-Ext-Sw-Vlan-59:
        received (in 3068365.134 secs):
                2959744703 packets      1349451335200 bytes
                0 pkts/sec      439001 bytes/sec
        transmitted (in 3068365.134 secs):
                2596168926 packets      1134033862376 bytes
                0 pkts/sec      369001 bytes/sec
      1 minute input rate 228 pkts/sec,  45747 bytes/sec
      1 minute output rate 211 pkts/sec,  83286 bytes/sec
      1 minute drop rate, 6 pkts/sec
      5 minute input rate 246 pkts/sec,  43807 bytes/sec
      5 minute output rate 240 pkts/sec,  119188 bytes/sec
      5 minute drop rate, 7 pkts/sec
VPN-Net:
        received (in 3067905.284 secs):
                9901688484 packets      4955599849823 bytes
                3000 pkts/sec   1615000 bytes/sec
        transmitted (in 3067905.284 secs):
                8640455568 packets      2462467806717 bytes
                2000 pkts/sec   802000 bytes/sec
      1 minute input rate 248 pkts/sec,  83497 bytes/sec
      1 minute output rate 240 pkts/sec,  22137 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 321 pkts/sec,  108490 bytes/sec
      5 minute output rate 309 pkts/sec,  27557 bytes/sec
      5 minute drop rate, 0 pkts/sec
intf9:
        received (in 3067905.284 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
        transmitted (in 3067905.284 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
      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
inside:
        received (in 3067906.014 secs):
                26356486931 packets     7042253139580 bytes
                8000 pkts/sec   2295000 bytes/sec
        transmitted (in 3067906.014 secs):
                34923086519 packets     19794670714738 bytes
                11001 pkts/sec  6452001 bytes/sec
      1 minute input rate 2514 pkts/sec,  548124 bytes/sec
      1 minute output rate 3215 pkts/sec,  1518420 bytes/sec
      1 minute drop rate, 6 pkts/sec
      5 minute input rate 2265 pkts/sec,  586875 bytes/sec
      5 minute output rate 2566 pkts/sec,  1394577 bytes/sec
      5 minute drop rate, 5 pkts/sec
intf5:
        received (in 3067906.004 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
        transmitted (in 3067906.004 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
      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
intf6:
        received (in 3067906.004 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
        transmitted (in 3067906.004 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
      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
state:
        received (in 3068366.204 secs):
                55749964 packets        57372118012 bytes
                1 pkts/sec      18000 bytes/sec
        transmitted (in 3068366.204 secs):
                790763475 packets       839418709074 bytes
                0 pkts/sec      273000 bytes/sec
      1 minute input rate 0 pkts/sec,  14 bytes/sec
      1 minute output rate 76 pkts/sec,  82296 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 0 pkts/sec,  15 bytes/sec
      5 minute output rate 75 pkts/sec,  80535 bytes/sec
      5 minute drop rate, 0 pkts/sec
Aggregated Traffic on Physical Interface
Ethernet0:
        received (in 3068366.994 secs):
                19574730130 packets     14284894983647 bytes
                6000 pkts/sec   4655000 bytes/sec
        transmitted (in 3068366.994 secs):
                15712458444 packets     5898581504412 bytes
                5000 pkts/sec   1922001 bytes/sec
      1 minute input rate 2719 pkts/sec,  1460117 bytes/sec
      1 minute output rate 2124 pkts/sec,  598829 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 2244 pkts/sec,  1453181 bytes/sec
      5 minute output rate 1925 pkts/sec,  579526 bytes/sec
      5 minute drop rate, 0 pkts/sec
Ethernet1:
        received (in 3068367.004 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
        transmitted (in 3068367.004 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
      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
Ethernet2:
        received (in 3068367.014 secs):
                9665491179 packets      5149730376935 bytes
                3000 pkts/sec   1678000 bytes/sec
        transmitted (in 3068367.014 secs):
                8525861215 packets      3772421554837 bytes
                2000 pkts/sec   1229000 bytes/sec
      1 minute input rate 441 pkts/sec,  117643 bytes/sec
      1 minute output rate 419 pkts/sec,  179534 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 511 pkts/sec,  147056 bytes/sec
      5 minute output rate 508 pkts/sec,  270643 bytes/sec
      5 minute drop rate, 0 pkts/sec
Ethernet3:
        received (in 3068368.524 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
        transmitted (in 3068368.524 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
      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
Ethernet4:
        received (in 3068368.534 secs):
                9895276598 packets      5094495866201 bytes
                3000 pkts/sec   1660001 bytes/sec
        transmitted (in 3068368.534 secs):
                8643187937 packets      2584256379980 bytes
                2000 pkts/sec   842000 bytes/sec
      1 minute input rate 245 pkts/sec,  87264 bytes/sec
      1 minute output rate 237 pkts/sec,  27905 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 321 pkts/sec,  113046 bytes/sec
      5 minute output rate 309 pkts/sec,  31966 bytes/sec
      5 minute drop rate, 0 pkts/sec
Ethernet5:
        received (in 3068368.534 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
        transmitted (in 3068368.534 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
      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
GigabitEthernet0:
        received (in 3068368.544 secs):
                26356499035 packets     7568258812849 bytes
                8000 pkts/sec   2466001 bytes/sec
        transmitted (in 3068368.544 secs):
                34923090773 packets     20453264933125 bytes
                11000 pkts/sec  6665000 bytes/sec
      1 minute input rate 2513 pkts/sec,  598366 bytes/sec
      1 minute output rate 3213 pkts/sec,  1576826 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 2265 pkts/sec,  630455 bytes/sec
      5 minute output rate 2566 pkts/sec,  1442769 bytes/sec
      5 minute drop rate, 0 pkts/sec
GigabitEthernet1:
        received (in 3068369.104 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
        transmitted (in 3068369.104 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
      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
GigabitEthernet2:
        received (in 3068369.114 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
        transmitted (in 3068369.114 secs):
                0 packets       0 bytes
                0 pkts/sec      0 bytes/sec
      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
GigabitEthernet3:
        received (in 3068369.124 secs):
                55750526 packets        59395158292 bytes
                1 pkts/sec      19000 bytes/sec
        transmitted (in 3068369.124 secs):
                790763663 packets       853658703052 bytes
                0 pkts/sec      278001 bytes/sec
      1 minute input rate 0 pkts/sec,  19 bytes/sec
      1 minute output rate 76 pkts/sec,  83700 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 0 pkts/sec,  20 bytes/sec
      5 minute output rate 75 pkts/sec,  81895 bytes/sec
      5 minute drop rate, 0 pkts/sec
sh perfmon
PERFMON STATS:                     Current      Average
Xlates                               17/s          0/s
Connections                         141/s          0/s
TCP Conns                            96/s          0/s
UDP Conns                            40/s          0/s
URL Access                            0/s          0/s
URL Server Req                        0/s          0/s
TCP Fixup                             1/s          0/s
TCP Intercept Established Conns       0/s          0/s
TCP Intercept Attempts                0/s          0/s
TCP Embryonic Conns Timeout          21/s          0/s
HTTP Fixup                            0/s          0/s
FTP Fixup                             0/s          0/s
AAA Authen                            0/s          0/s
AAA Author                            0/s          0/s
AAA Account                           0/s          0/s
VALID CONNS RATE in TCP INTERCEPT:    Current      Average
                                       100.00%         99.00%
sh blocks
  SIZE    MAX    LOW    CNT
     0    600    525    600
     4    100     99     99
    80    700    607    700
   256   1636   1071   1636
  1550  12818      0  11023
  2048    100     98    100
  2560     40     39     40
  4096     30     29     30
  8192     60     60     60
16384    110    110    110
65536     10     10     10
sh memory
Free memory:       423746152 bytes (39%)
Used memory:       649995672 bytes (61%)
Total memory:     1073741824 bytes (100%)
sh xlate
1728 in use, 7811 most used
Global 172.33.24.4 Local 10.21.250.1
Global 192.118.67.119 Local 10.20.56.27
Global 192.118.67.35 Local 10.20.56.22
Global 192.118.67.33 Local 10.20.56.31
Global 192.118.67.41 Local 10.20.56.32
Global 192.118.67.115 Local 10.20.56.33
Global 192.118.67.21 Local 10.20.59.11
Global 192.118.67.103 Local 10.20.59.14
Global 192.118.67.116 Local 10.20.56.18
Global 192.118.67.32 Local 10.20.58.26
Global 192.118.67.37 Local 10.20.58.27
Global 192.118.67.100 Local 10.20.56.30
Global 192.118.67.104 Local 10.20.58.13
Global 192.118.67.36 Local 10.20.57.220
Global 192.118.67.113 Local 10.20.57.221
Global 192.118.67.112 Local 10.20.57.222
Global 192.118.67.109 Local 10.20.58.16
Global 192.118.67.110 Local 10.20.58.17
Global 192.118.67.111 Local 10.20.58.18
Global 192.118.67.108 Local 10.20.59.211
Global 192.118.67.101 Local 10.20.56.101
Global 192.118.67.5 Local 10.20.56.25
Global 192.118.67.70 Local 10.20.208.10
Global 192.118.67.71 Local 10.20.208.11
Global 192.118.67.105 Local 10.20.59.210
Global 192.118.67.72 Local 10.20.208.12
Global 192.118.67.22 Local 10.20.59.12
Global 192.118.67.160 Local 10.20.58.12
Global 192.118.67.73 Local 10.20.208.13
Global 192.118.67.51 Local 10.20.56.253
Global 192.118.67.52 Local 10.20.56.54
Global 192.118.67.16 Local 10.20.59.16
Global 192.118.67.54 Local 10.20.59.17
Global 192.118.67.55 Local 10.20.59.15
Global 192.118.67.56 Local 10.20.208.21
Global 192.118.67.64 Local 10.20.59.22
Global 192.118.67.65 Local 10.20.59.23
Global 192.118.67.66 Local 10.20.59.24
Global 192.118.67.67 Local 10.20.59.25
Global 192.118.67.57 Local 10.20.208.22
Global 192.118.67.68 Local 10.20.59.26
Global 192.118.67.12 Local 10.20.59.21
Global 192.118.67.69 Local 10.20.59.28
Global 192.118.67.58 Local 10.20.59.18
Global 192.118.67.59 Local 10.20.59.19
Global 192.118.67.30 Local 10.20.59.30
Global 192.118.67.61 Local 10.20.59.32
Global 192.118.67.74 Local 10.20.59.29
Global 192.118.67.11 Local 10.20.59.20
Global 192.118.67.62 Local 10.20.208.23
Global 192.118.67.75 Local 10.20.208.25
Global 192.118.67.76 Local 10.20.59.36
Global 192.118.67.77 Local 10.20.59.37
Global 192.118.67.78 Local 10.20.208.26
Global 192.118.67.79 Local 10.20.59.40
Global 192.118.67.80 Local 10.20.208.27
Global 192.118.67.81 Local 10.20.208.28
Global 192.118.67.82 Local 10.20.208.29
Global 192.118.67.83 Local 10.20.208.30
Global 192.118.67.84 Local 10.20.59.38
Global 192.118.67.85 Local 10.20.59.39
Global 192.118.67.86 Local 10.20.59.41
Global 192.118.67.87 Local 10.20.59.42
Global 192.118.67.89 Local 10.20.208.31
Global 192.118.67.45 Local 10.20.59.45
Global 192.118.67.46 Local 10.20.59.46
Global 192.118.67.47 Local 10.20.59.43
Global 192.118.67.48 Local 10.20.59.50
Global 192.118.67.60 Local 10.20.59.47
Global 192.118.67.123 Local 10.20.59.59
Global 192.118.67.63 Local 10.20.208.24
Global 192.118.67.90 Local 10.20.208.32
Global 192.118.67.124 Local 10.20.57.16
Global 192.118.67.125 Local 10.20.57.17
Global 192.118.67.126 Local 10.20.57.18
Global 192.118.67.91 Local 10.20.208.33
Global 192.118.67.92 Local 10.20.208.34
Global 192.118.67.93 Local 10.20.208.35
Global 192.118.67.94 Local 10.20.208.36
Global 192.118.67.95 Local 10.20.208.37
Global 192.118.67.96 Local 10.20.208.38
Global 192.118.67.97 Local 10.20.208.39
Global 192.118.67.98 Local 10.20.208.40
Global 192.118.67.99 Local 10.20.208.41
Global 192.118.67.106 Local 10.20.208.42
Global 192.118.67.107 Local 10.20.208.43
Global 192.118.67.127 Local 10.20.208.44
Global 192.118.67.128 Local 10.20.208.45
Global 192.118.67.102 Local 10.20.59.49
Global 192.118.67.129 Local 10.20.208.46
Global 192.118.67.130 Local 10.20.208.47
Global 192.118.67.217 Local 10.20.208.48
Global 192.118.67.221 Local 10.20.208.52
Global 192.118.67.114 Local 10.20.56.13
Global 192.118.67.222 Local 10.20.208.53
Global 192.118.67.223 Local 10.20.208.55
Global 192.118.67.224 Local 10.20.208.56
Global 192.118.67.225 Local 10.20.208.58
Global 192.118.67.226 Local 10.20.208.59
Global 192.118.67.132 Local 10.20.59.60
Global 192.118.67.20 Local 10.20.59.31
Global 192.118.67.227 Local 10.20.56.35
Global 192.118.67.133 Local 10.20.59.57
Global 192.118.67.134 Local 10.20.59.54
Global 192.118.67.135 Local 10.20.59.53
Global 192.118.67.136 Local 10.20.59.64
Global 192.118.67.137 Local 10.20.59.65
Global 192.118.67.138 Local 10.20.59.66
Global 192.118.67.139 Local 10.20.59.33
Global 192.118.67.140 Local 10.20.208.61
Global 192.118.67.141 Local 10.20.208.62
Global 192.118.67.228 Local 10.20.208.63
Global 192.118.67.229 Local 10.20.208.64
Global 192.118.67.230 Local 10.20.208.65
Global 192.118.67.142 Local 10.20.57.19
Global 192.118.67.143 Local 10.20.57.20
Global 192.118.67.144 Local 10.20.208.66
Global 192.118.67.145 Local 10.20.208.67
Global 192.118.67.146 Local 10.20.208.68
Global 192.118.67.147 Local 10.20.208.69
Global 192.118.67.148 Local 10.20.208.70
Global 192.118.67.149 Local 10.20.208.71
Global 192.118.67.150 Local 10.20.208.72
Global 192.118.67.151 Local 10.20.208.73
Global 192.118.67.152 Local 10.20.208.76
Global 192.118.67.153 Local 10.20.208.77
Global 192.118.67.154 Local 10.20.208.78
Global 192.118.67.155 Local 10.20.208.79
Global 192.118.67.156 Local 10.20.208.80
Global 192.118.67.157 Local 10.20.208.81
Global 192.118.67.158 Local 10.20.208.82
Global 192.118.67.159 Local 10.20.208.83
Global 192.118.67.163 Local 10.20.208.86
Global 192.118.67.161 Local 10.20.208.87
Global 192.118.67.231 Local 10.20.56.56
Global 192.118.67.162 Local 10.20.56.40
Global 192.118.67.164 Local 10.20.208.88
Global 192.118.67.165 Local 10.20.56.235
Global 192.118.67.166 Local 10.20.208.91
Global 192.118.67.168 Local 10.20.208.92
Global 192.118.67.169 Local 10.20.208.95
Global 192.118.67.170 Local 10.20.208.96
Global 192.118.67.173 Local 10.20.59.72
Global 192.118.67.174 Local 10.20.59.73
Global 192.118.67.176 Local 10.20.59.75
Global 192.118.67.177 Local 10.20.59.79
Global 192.118.67.178 Local 10.20.59.81
Global 192.118.67.179 Local 10.20.59.82
Global 192.118.67.180 Local 10.20.59.83
Global 192.118.67.181 Local 10.20.59.84
Global 192.118.67.182 Local 10.20.59.85
Global 192.118.67.171 Local 10.20.208.97
Global 192.118.67.183 Local 10.20.208.98
Global 192.118.67.184 Local 10.20.208.99
Global 192.118.67.185 Local 10.20.208.100
Global 192.118.67.186 Local 10.20.59.55
Global 192.118.67.200 Local 10.20.59.110
Global 192.118.67.201 Local 10.20.59.111
Global 192.118.67.202 Local 10.20.59.112
Global 192.118.67.203 Local 10.20.59.87
Global 192.118.67.204 Local 10.20.208.101
Global 192.118.67.205 Local 10.20.208.102
Global 192.118.67.206 Local 10.20.208.103
Global 192.118.67.207 Local 10.20.208.104
Global 192.118.67.208 Local 10.20.208.105
Global 192.118.67.209 Local 10.20.208.106
Global 192.118.67.210 Local 10.20.208.107
Global 192.118.67.211 Local 10.20.56.39
Global 192.118.67.120 Local 10.20.59.34
Global 192.118.67.187 Local 10.20.59.89
Global 192.118.67.188 Local 10.20.208.108
Global 192.118.67.189 Local 10.20.208.109
Global 192.118.67.190 Local 10.20.208.110
Global 192.118.67.191 Local 10.20.208.111
Global 192.118.67.192 Local 10.20.208.112
Global 192.118.67.193 Local 10.20.208.113
Global 192.118.67.194 Local 10.20.208.114
Global 192.118.67.195 Local 10.20.208.115
Global 192.118.67.196 Local 10.20.208.116
Global 192.118.67.172 Local 10.20.208.123
Global 192.118.67.198 Local 10.20.59.90
Global 192.118.67.232 Local 10.20.58.30
Global 192.118.67.233 Local 10.20.58.31
Global 192.118.67.234 Local 10.20.58.32
Global 192.118.67.235 Local 10.20.58.33
Global 192.118.67.236 Local 10.20.58.34
Global 192.118.67.237 Local 10.20.58.35
Global 192.118.67.238 Local 10.20.58.36
Global 192.118.67.199 Local 10.20.208.199
Global 192.118.67.212 Local 10.20.59.188
Global 192.118.67.239 Local 10.20.58.37
Global 192.118.67.197 Local 10.20.56.42
Global 192.118.67.213 Local 10.20.208.93
Global 192.118.67.240 Local 10.20.56.21
Global 192.118.67.215 Local 10.20.208.119
Global 192.118.67.218 Local 10.20.208.120
Global 192.118.67.242 Local 10.20.59.91
Global 192.118.67.243 Local 10.20.59.92
Global 192.118.67.244 Local 10.20.208.124
Global 192.118.67.246 Local 10.20.208.125
Global 192.118.67.219 Local 10.20.208.121
Global 192.118.67.50 Local 10.20.208.122
Global 192.118.67.247 Local 10.20.208.126
Global 192.118.67.248 Local 10.20.59.120
Global 192.118.67.117 Local 10.20.58.38
Global 192.118.67.39 Local 10.20.56.156
Global 192.118.67.40 Local 10.20.59.99
Global 192.118.67.26 Local 10.20.208.15
Global 192.118.67.27 Local 10.20.208.16
Global 192.118.67.17 Local 10.20.59.101
Global 192.118.67.249 Local 10.20.59.100
Global 192.118.67.28 Local 10.20.208.17
Global 192.118.67.31 Local 10.20.208.137
Global 192.118.67.131 Local 10.20.208.138
Global 192.118.67.13 Local 10.20.208.139
Global 192.118.67.14 Local 10.20.208.140
Global 192.118.67.38 Local 10.20.59.212
Global 192.118.67.167 Local 10.20.59.114
Global 192.118.67.29 Local 10.20.59.121
Global 192.118.67.34 Local 10.20.59.127
Global 192.118.67.42 Local 10.20.59.128
Global 192.118.67.43 Local 10.20.59.129
Global 192.118.67.175 Local 10.20.59.119
Global 192.118.64.23 Local 10.20.208.141
Global 192.118.67.23 Local 10.20.56.90
Global 192.118.67.19 Local 10.20.208.18
Global 192.118.67.15 Local 10.20.208.9
Global 192.118.67.214 Local 10.20.59.108
Global 192.118.64.11 Local 10.20.208.127
Global 192.118.64.13 Local 10.20.208.94
Global 192.118.67.49 Local 10.20.56.14
Global 192.118.65.12 Local 10.20.208.228
Global 192.118.64.14 Local 10.20.208.229
Global 192.118.65.14 Local 10.20.208.130
Global 192.118.65.15 Local 10.20.208.131
Global 192.118.64.32 Local 10.20.208.132
Global 192.118.64.33 Local 10.20.208.142
Global 192.118.64.35 Local 10.20.59.135
Global 192.118.64.37 Local 10.20.59.136
Global 192.118.67.251 Local 10.20.5.39
Global 192.118.67.252 Local 10.20.5.40
Global 192.118.67.216 Local 10.20.3.16
Global 192.118.67.220 Local 10.20.5.53
Global 192.118.67.250 Local 10.20.2.250
Global 192.118.67.241 Local 10.20.61.224
Global 192.118.67.53 Local 10.20.5.176
Global 192.118.67.253 Local 10.20.2.253
Global 192.118.64.50 Local 10.21.40.11
Global 192.118.64.51 Local 10.21.40.12
Global 192.118.64.52 Local 10.21.40.13
Global 192.118.64.53 Local 10.21.48.14
Global 192.118.64.54 Local 10.21.12.150
Global 192.118.64.55 Local 10.21.12.20
Global 192.118.64.16 Local 10.21.12.16
Global 192.118.64.17 Local 10.21.12.17
Global 192.118.64.18 Local 10.21.12.13
Global 192.118.64.19 Local 10.21.12.14
Global 192.118.64.20 Local 10.21.12.11
Global 192.118.64.21 Local 10.21.12.12
Global 192.118.64.22 Local 10.21.12.24
Global 192.118.64.31 Local 10.21.12.23
Global 192.118.64.56 Local 10.21.69.13
Global 192.118.64.38 Local 10.21.12.37
Global 192.118.67.245 Local 10.210.240.163
Global 192.118.64.57 Local 10.20.59.138
Global 192.118.64.58 Local 10.20.208.143
Global 192.118.64.59 Local 10.20.208.144
Global 192.118.64.60 Local 10.20.208.145
Global 192.118.64.61 Local 10.20.208.146
Global 192.118.64.62 Local 10.20.208.147
Global 192.118.64.63 Local 10.20.208.148
Global 192.118.64.64 Local 10.20.208.149
Global 192.118.64.65 Local 10.20.208.150
Global 192.118.64.66 Local 10.20.208.151
Global 192.118.64.67 Local 10.20.208.152
Global 192.118.64.68 Local 10.20.208.153
Global 192.118.64.41 Local 10.21.12.28
Global 192.118.64.39 Local 10.21.12.38
Global 192.118.64.40 Local 10.21.12.39
Global 192.118.64.42 Local 10.21.12.31
Global 192.118.64.43 Local 10.21.12.32
Global 192.118.64.44 Local 10.21.12.33
Global 192.118.64.69 Local 10.20.208.154
Global 192.118.64.70 Local 10.20.208.250
Global 192.118.64.45 Local 10.20.56.19
Global 192.118.64.71 Local 10.20.56.50
Global 192.118.64.46 Local 10.20.59.137
Global 192.118.67.44 Local 10.20.59.131
Global 192.118.64.72 Local 10.20.208.155
Global 192.118.64.73 Local 10.20.59.139
Global 192.118.64.74 Local 10.20.59.140
Global 192.118.64.47 Local 10.20.208.133
Global 192.118.64.75 Local 10.20.59.141
Global 192.118.64.76 Local 10.20.59.142
Global 192.118.64.48 Local 10.20.208.230
Global 192.118.67.118 Local 10.20.58.40
Global 192.118.64.77 Local 10.20.58.44
Global 192.118.64.78 Local 10.20.208.231
Global 192.118.64.79 Local 10.20.208.232
Global 192.118.64.80 Local 10.20.208.233
Global 192.118.64.81 Local 10.20.208.234
Global 192.118.64.85 Local 10.20.56.55
Global 192.118.64.82 Local 10.20.208.235
Global 192.118.64.83 Local 10.20.208.236
Global 192.118.64.84 Local 10.20.208.237
Global 192.118.64.88 Local 10.20.58.45
Global 192.118.64.87 Local 10.20.208.238
Global 192.118.64.94 Local 10.20.208.181
Global 172.18.8.128 Local 10.20.168.25
Global 192.118.64.86 Local 10.20.56.37
Global 192.118.64.96 Local 10.20.58.46
Global 192.118.64.89 Local 10.20.59.144
Global 192.118.64.95 Local 10.20.59.150
Global 192.118.64.98 Local 10.20.208.183
Global 192.118.64.99 Local 10.20.208.184
Global 192.118.64.97 Local 10.20.208.182
Global 192.118.64.100 Local 10.20.59.151
Global 192.118.64.101 Local 10.20.208.185
Global 192.118.64.102 Local 10.20.208.186
Global 192.118.64.103 Local 10.20.208.187
Global 192.118.64.104 Local 10.20.208.188
Global 192.118.64.105 Local 10.20.208.189
Global 192.118.64.106 Local 10.20.208.190
Global 192.118.64.107 Local 10.20.208.191
Global 192.118.64.108 Local 10.20.208.192
Global 192.118.64.109 Local 10.20.208.193
Global 192.118.64.110 Local 10.20.59.145
Global 192.118.64.111 Local 10.20.208.194
Global 192.118.64.112 Local 10.20.208.195
Global 192.118.64.113 Local 10.20.208.196
Global 192.118.64.114 Local 10.20.59.152
Global 192.118.64.116 Local 10.20.208.197
Global 192.118.64.117 Local 10.20.59.146
Global 192.118.64.119 Local 10.20.59.147
Global 192.118.64.124 Local 10.20.208.198
Global 192.118.64.120 Local 10.20.208.200
Global 192.118.64.121 Local 10.20.208.201
Global 192.118.64.123 Local 10.20.208.203
Global 192.118.64.122 Local 10.20.208.202
Global 192.118.64.115 Local 10.20.59.155
Global 192.118.64.127 Local 10.20.59.159
Global 192.118.64.129 Local 10.21.12.45
Global 192.118.64.130 Local 10.20.56.51
Global 192.118.64.132 Local 10.20.59.160
Global 192.118.64.133 Local 10.21.12.49
Global 192.118.64.134 Local 10.21.12.50
Global 192.118.64.34 Local 10.20.58.100
Global 192.118.64.135 Local 10.21.200.69
Global 192.118.64.128 Local 10.21.40.14
Global 192.118.64.136 Local 10.21.12.51
Global 192.118.64.137 Local 10.21.12.52
Global 192.118.64.138 Local 10.21.12.56
Global 192.118.64.139 Local 10.21.12.57
Global 192.118.64.140 Local 10.21.12.58
Global 192.118.64.141 Local 10.21.12.59
Global 192.118.64.142 Local 10.20.108.94
Global 192.118.64.143 Local 10.21.12.54
Global 192.118.64.144 Local 10.21.12.55
Global 192.118.64.145 Local 10.20.59.164
Global 192.118.64.146 Local 10.20.59.165
Global 192.118.64.148 Local 10.20.56.48
Global 192.118.64.147 Local 10.21.12.60
Global 192.118.65.132 Local 10.20.208.167
Global 192.118.65.142 Local 10.20.208.166
Global 192.118.65.150 Local 10.20.208.163
Global 192.118.65.151 Local 10.20.208.164
Global 192.118.65.152 Local 10.20.208.165
Global 192.118.65.160 Local 10.20.208.160
Global 192.118.65.161 Local 10.20.208.161
Global 192.118.65.162 Local 10.20.208.162
Global 192.118.64.150 Local 10.20.56.57
Global 192.118.64.149 Local 10.20.208.134
Global 192.118.64.151 Local 10.21.20.87
Global 192.118.64.152 Local 10.21.20.20
Global 192.118.64.153 Local 10.21.20.11
PAT Global 192.118.64.254(19796) Local 10.21.20.52(24138)
PAT Global 192.118.64.254(16357) Local 10.21.20.52(64376)
PAT Global 192.118.64.254(19202) Local 10.20.152.170(19808)
PAT Global 192.118.64.254(19201) Local 10.20.152.170(19807)
PAT Global 192.118.64.254(29800) Local 10.20.137.159(52612)
PAT Global 192.118.64.254(29798) Local 10.20.137.159(52611)
PAT Global 192.118.64.254(17008) Local 10.20.5.62(36086)
PAT Global 192.118.64.254(29804) Local 10.20.5.62(61713)
PAT Global 192.118.64.25(15795) Local 10.20.5.69(2779)
PAT Global 192.118.64.25(15794) Local 10.20.5.69(2778)
PAT Global 192.118.64.25(15793) Local 10.20.5.69(2776)
PAT Global 192.118.64.25(15785) Local 10.20.5.69(2775)
PAT Global 192.118.64.25(15784) Local 10.20.5.69(2774)
PAT Global 192.118.64.25(15783) Local 10.20.5.69(2772)
PAT Global 192.118.64.25(15775) Local 10.20.5.69(2771)
PAT Global 192.118.64.25(15774) Local 10.20.5.69(2770)
PAT Global 192.118.64.25(15773) Local 10.20.5.69(2768)
PAT Global 192.118.64.25(15765) Local 10.20.5.69(2767)
PAT Global 192.118.64.25(15764) Local 10.20.5.69(2766)
PAT Global 192.118.64.25(15763) Local 10.20.5.69(2764)
PAT Global 192.118.64.25(15755) Local 10.20.5.69(2763)
PAT Global 192.118.64.25(15754) Local 10.20.5.69(2762)
PAT Global 192.118.64.25(15753) Local 10.20.5.69(2760)
PAT Global 192.118.64.254(19803) Local 10.20.3.230(4686)
PAT Global 192.118.64.254(19807) Local 10.20.221.72(53232)
PAT Global 192.118.64.254(19806) Local 10.20.221.72(53231)
PAT Global 192.118.64.254(19805) Local 10.20.221.72(53228)
PAT Global 192.118.64.254(19804) Local 10.20.221.72(53204)
PAT Global 192.118.64.254(60414) Local 10.20.5.68(59166)
PAT Global 192.118.64.254(60405) Local 10.20.5.68(59165)
PAT Global 192.118.64.254(60402) Local 10.20.5.68(59164)
PAT Global 192.118.64.254(60294) Local 10.20.5.68(59163)
PAT Global 192.118.64.254(60054) Local 10.20.5.68(59159)
PAT Global 192.118.64.254(59968) Local 10.20.5.68(59158)
PAT Global 192.118.64.254(59817) Local 10.20.5.68(59154)
PAT Global 192.118.64.254(59813) Local 10.20.5.68(59153)
PAT Global 192.118.64.254(59680) Local 10.20.5.68(59150)
PAT Global 192.118.64.254(59583) Local 10.20.5.68(59149)
PAT Global 192.118.64.254(59474) Local 10.20.5.68(59148)
PAT Global 192.118.64.30(1104) Local 10.20.155.130(21520)
PAT Global 192.118.64.254(19815) Local 10.20.5.95(55449)
PAT Global 192.118.64.254(19811) Local 10.20.5.95(55448)
PAT Global 192.118.64.254(8142) Local 10.20.221.65(55153)
PAT Global 192.118.64.254(8141) Local 10.20.221.65(55150)
PAT Global 192.118.64.254(8138) Local 10.20.221.65(55122)
PAT Global 192.118.64.254(8137) Local 10.20.221.65(55121)
PAT Global 192.118.64.254(6654) Local 10.20.221.65(49761)
PAT Global 192.118.64.254(6653) Local 10.20.221.65(49760)
PAT Global 192.118.64.254(10452) Local 10.20.137.43(50238)
PAT Global 192.118.67.121(31730) Local 10.20.32.15(59198)
PAT Global 192.118.67.121(31729) Local 10.20.32.15(59197)
PAT Global 192.118.67.121(31728) Local 10.20.32.15(59196)
PAT Global 192.118.67.121(31727) Local 10.20.32.15(59195)
PAT Global 192.118.67.121(31726) Local 10.20.32.15(59194)
PAT Global 192.118.67.121(31725) Local 10.20.32.15(59083)
PAT Global 192.118.67.121(31724) Local 10.20.32.15(59082)
PAT Global 192.118.67.121(31723) Local 10.20.32.15(59081)
PAT Global 192.118.67.121(31722) Local 10.20.32.15(59080)
PAT Global 192.118.67.121(31721) Local 10.20.32.15(59079)
PAT Global 192.118.67.121(31720) Local 10.20.32.15(58962)
PAT Global 192.118.67.121(31719) Local 10.20.32.15(58961)
PAT Global 192.118.67.121(31718) Local 10.20.32.15(58960)
PAT Global 192.118.67.121(31717) Local 10.20.32.15(58959)
PAT Global 192.118.67.121(31716) Local 10.20.32.15(58958)
PAT Global 192.118.67.121(31715) Local 10.20.32.15(58957)
PAT Global 192.118.67.121(50377) Local 10.20.32.15(55515)
PAT Global 192.118.67.121(31714) Local 10.20.32.15(58395)
PAT Global 192.118.67.121(31713) Local 10.20.32.15(58370)
PAT Global 192.118.67.121(31712) Local 10.20.32.15(58345)
PAT Global 192.118.67.121(31711) Local 10.20.32.15(58344)
PAT Global 192.118.67.121(31710) Local 10.20.32.15(58343)
PAT Global 192.118.67.121(31709) Local 10.20.32.15(58342)
PAT Global 192.118.67.121(31708) Local 10.20.32.15(58315)
PAT Global 192.118.67.121(31707) Local 10.20.32.15(58279)
PAT Global 192.118.67.121(31706) Local 10.20.32.15(54798)
PAT Global 192.118.67.121(31705) Local 10.20.32.15(54797)
PAT Global 192.118.67.121(31704) Local 10.20.32.15(54796)
PAT Global 192.118.67.121(31703) Local 10.20.32.15(54795)
PAT Global 192.118.67.121(31702) Local 10.20.32.15(54616)
PAT Global 192.118.67.121(31701) Local 10.20.32.15(54604)
PAT Global 192.118.67.121(31700) Local 10.20.32.15(54600)
PAT Global 192.118.67.121(31699) Local 10.20.32.15(54588)
PAT Global 192.118.67.121(31698) Local 10.20.32.15(54565)
PAT Global 192.118.67.121(31697) Local 10.20.32.15(54089)
PAT Global 192.118.67.121(31696) Local 10.20.32.15(54026)
PAT Global 192.118.67.121(31695) Local 10.20.32.15(53901)
PAT Global 192.118.67.121(31694) Local 10.20.32.15(53900)
PAT Global 192.118.67.121(31693) Local 10.20.32.15(53899)
PAT Global 192.118.67.121(31692) Local 10.20.32.15(53898)
PAT Global 192.118.67.121(31691) Local 10.20.32.15(53897)
PAT Global 192.118.67.121(31690) Local 10.20.32.15(53896)
PAT Global 192.118.67.121(31689) Local 10.20.32.15(53895)
PAT Global 192.118.67.121(31688) Local 10.20.32.15(53894)
PAT Global 192.118.67.121(31687) Local 10.20.32.15(53785)
PAT Global 192.118.67.121(31686) Local 10.20.32.15(53693)
PAT Global 192.118.67.121(31685) Local 10.20.32.15(53692)
PAT Global 192.118.67.121(31684) Local 10.20.32.15(53691)
PAT Global 192.118.67.121(31683) Local 10.20.32.15(53690)
PAT Global 192.118.67.121(31682) Local 10.20.32.15(53689)
PAT Global 192.118.67.121(31681) Local 10.20.32.15(53652)
PAT Global 192.118.67.121(31680) Local 10.20.32.15(53555)
PAT Global 192.118.67.121(31679) Local 10.20.32.15(53554)
PAT Global 192.118.67.121(31678) Local 10.20.32.15(53553)
PAT Global 192.118.67.121(31677) Local 10.20.32.15(53552)
PAT Global 192.118.67.121(31676) Local 10.20.32.15(53551)
PAT Global 192.118.67.121(31675) Local 10.20.32.15(53521)
PAT Global 192.118.67.121(31674) Local 10.20.32.15(53520)
PAT Global 192.118.67.121(31673) Local 10.20.32.15(53519)
PAT Global 192.118.67.121(31672) Local 10.20.32.15(53518)
PAT Global 192.118.67.121(31671) Local 10.20.32.15(53517)
PAT Global 192.118.67.121(31670) Local 10.20.32.15(53516)
PAT Global 192.118.67.121(31669) Local 10.20.32.15(53515)
PAT Global 192.118.67.121(31668) Local 10.20.32.15(53514)
PAT Global 192.118.67.121(31667) Local 10.20.32.15(53447)
PAT Global 192.118.67.121(31666) Local 10.20.32.15(53446)
PAT Global 192.118.67.121(31665) Local 10.20.32.15(53445)
PAT Global 192.118.67.121(31664) Local 10.20.32.15(53444)
PAT Global 192.118.67.121(31663) Local 10.20.32.15(53443)
PAT Global 192.118.67.121(31662) Local 10.20.32.15(53442)
PAT Global 192.118.67.121(31661) Local 10.20.32.15(53376)
PAT Global 192.118.67.121(31660) Local 10.20.32.15(53375)
PAT Global 192.118.67.121(31659) Local 10.20.32.15(53374)
PAT Global 192.118.67.121(31658) Local 10.20.32.15(53373)
PAT Global 192.118.67.121(31657) Local 10.20.32.15(53372)
PAT Global 192.118.67.121(31656) Local 10.20.32.15(53371)
PAT Global 192.118.67.121(31655) Local 10.20.32.15(53370)
PAT Global 192.118.67.121(31654) Local 10.20.32.15(53369)
PAT Global 192.118.67.121(31653) Local 10.20.32.15(53368)
PAT Global 192.118.67.121(31652) Local 10.20.32.15(52952)
PAT Global 192.118.67.121(31651) Local 10.20.32.15(52951)
PAT Global 192.118.67.121(31650) Local 10.20.32.15(52950)
PAT Global 192.118.67.121(31649) Local 10.20.32.15(52949)
PAT Global 192.118.67.121(31648) Local 10.20.32.15(52948)
PAT Global 192.118.67.121(31647) Local 10.20.32.15(52827)
PAT Global 192.118.67.121(31646) Local 10.20.32.15(52826)
PAT Global 192.118.67.121(31645) Local 10.20.32.15(52825)
PAT Global 192.118.67.121(31644) Local 10.20.32.15(52824)
PAT Global 192.118.67.121(31643) Local 10.20.32.15(52822)
PAT Global 192.118.67.121(31642) Local 10.20.32.15(52784)
PAT Global 192.118.67.121(31641) Local 10.20.32.15(52779)
PAT Global 192.118.67.121(31640) Local 10.20.32.15(52778)
PAT Global 192.118.67.121(31639) Local 10.20.32.15(52777)
PAT Global 192.118.67.121(31638) Local 10.20.32.15(52776)
PAT Global 192.118.67.121(31637) Local 10.20.32.15(52775)
PAT Global 192.118.67.121(31636) Local 10.20.32.15(52773)
PAT Global 192.118.67.121(31635) Local 10.20.32.15(52772)
PAT Global 192.118.67.121(31634) Local 10.20.32.15(52771)
PAT Global 192.118.67.121(31633) Local 10.20.32.15(52682)
PAT Global 192.118.67.121(31632) Local 10.20.32.15(62544)
PAT Global 192.118.67.121(31631) Local 10.20.32.15(62483)
PAT Global 192.118.67.121(31630) Local 10.20.32.15(62458)
PAT Global 192.118.67.121(31629) Local 10.20.32.15(62410)
PAT Global 192.118.64.25(25474) Local 10.20.168.20(57228)
PAT Global 192.118.64.25(25473) Local 10.20.168.20(57227)
PAT Global 192.118.64.25(25472) Local 10.20.168.20(57226)
PAT Global 192.118.64.25(25471) Local 10.20.168.20(57225)
PAT Global 192.118.64.25(25470) Local 10.20.168.20(57224)
PAT Global 192.118.64.25(25469) Local 10.20.168.20(57223)
PAT Global 192.118.64.25(25468) Local 10.20.168.20(57222)
PAT Global 192.118.64.25(25467) Local 10.20.168.20(57221)
PAT Global 192.118.64.25(25466) Local 10.20.168.20(57220)
PAT Global 192.118.64.25(25465) Local 10.20.168.20(57219)
PAT Global 192.118.64.25(25464) Local 10.20.168.20(57218)
PAT Global 192.118.64.25(25463) Local 10.20.168.20(57217)
PAT Global 192.118.64.25(25462) Local 10.20.168.20(57216)
PAT Global 192.118.64.25(25461) Local 10.20.168.20(57215)
PAT Global 192.118.64.25(25460) Local 10.20.168.20(57214)
PAT Global 192.118.64.25(25459) Local 10.20.168.20(57213)
PAT Global 192.118.64.25(25458) Local 10.20.168.20(57212)
PAT Global 192.118.64.25(25457) Local 10.20.168.20(57211)
PAT Global 192.118.64.25(25456) Local 10.20.168.20(57210)
PAT Global 192.118.64.25(25455) Local 10.20.168.20(57209)
PAT Global 192.118.64.25(25454) Local 10.20.168.20(57208)
PAT Global 192.118.64.25(25453) Local 10.20.168.20(57207)
PAT Global 192.118.64.25(25452) Local 10.20.168.20(57206)
PAT Global 192.118.64.25(25451) Local 10.20.168.20(57205)
PAT Global 192.118.64.25(25450) Local 10.20.168.20(57204)
PAT Global 192.118.64.25(25449) Local 10.20.168.20(57203)
PAT Global 192.118.64.25(25448) Local 10.20.168.20(57202)
PAT Global 192.118.64.25(25447) Local 10.20.168.20(57201)
PAT Global 192.118.64.25(25446) Local 10.20.168.20(57200)
PAT Global 192.118.64.25(25445) Local 10.20.168.20(57199)
PAT Global 192.118.64.25(25444) Local 10.20.168.20(57198)
PAT Global 192.118.64.25(25443) Local 10.20.168.20(57197)
PAT Global 192.118.64.25(25442) Local 10.20.168.20(57196)
PAT Global 192.118.64.25(25441) Local 10.20.168.20(57188)
PAT Global 192.118.64.25(25440) Local 10.20.168.20(57133)
PAT Global 192.118.64.25(9235) Local 10.20.168.20(49358)
PAT Global 192.118.64.254(11355) Local 10.20.169.147(34976)
PAT Global 192.118.64.254(44134) Local 10.20.169.147(31893)
PAT Global 192.118.64.254(42500) Local 10.20.169.147(31864)
PAT Global 192.118.64.254(39385) Local 10.20.169.147(31798)
PAT Global 192.118.64.254(31946) Local 10.20.169.147(31660)
PAT Global 192.118.64.254(19781) Local 10.20.152.219(15508)
PAT Global 192.118.64.254(18293) Local 10.20.152.30(49571)
PAT Global 192.118.64.254(18275) Local 10.20.152.30(49566)
PAT Global 192.118.64.25(9238) Local 10.20.168.25(49279)
PAT Global 192.118.65.11(33972) Local 10.20.155.84(53808)
PAT Global 192.118.65.11(33971) Local 10.20.155.84(53807)
PAT Global 192.118.65.11(33969) Local 10.20.155.84(53799)
PAT Global 192.118.65.11(33968) Local 10.20.155.84(53798)
PAT Global 192.118.65.11(30670) Local 10.20.155.67(33346)
PAT Global 192.118.65.11(30669) Local 10.20.155.67(33344)
PAT Global 192.118.64.25(15802) Local 10.20.168.17(54163)
PAT Global 192.118.64.25(15801) Local 10.20.168.17(54162)
PAT Global 192.118.64.25(15800) Local 10.20.168.17(54161)
PAT Global 192.118.64.25(15799) Local 10.20.168.17(54160)
PAT Global 192.118.64.25(15798) Local 10.20.168.17(54152)
PAT Global 192.118.64.25(15797) Local 10.20.168.17(54151)
PAT Global 192.118.64.25(15796) Local 10.20.168.17(54133)
PAT Global 192.118.64.25(15792) Local 10.20.168.17(54125)
PAT Global 192.118.64.25(15791) Local 10.20.168.17(54124)
PAT Global 192.118.64.25(15790) Local 10.20.168.17(54123)
PAT Global 192.118.64.25(15789) Local 10.20.168.17(54121)
PAT Global 192.118.64.25(15788) Local 10.20.168.17(54114)
PAT Global 192.118.64.25(15787) Local 10.20.168.17(54109)
PAT Global 192.118.64.25(15786) Local 10.20.168.17(54095)
PAT Global 192.118.64.25(15782) Local 10.20.168.17(54087)
PAT Global 192.118.64.25(15781) Local 10.20.168.17(54086)
PAT Global 192.118.64.25(15780) Local 10.20.168.17(54084)
PAT Global 192.118.64.25(15779) Local 10.20.168.17(50304)
PAT Global 192.118.64.25(15778) Local 10.20.168.17(50302)
PAT Global 192.118.64.25(15777) Local 10.20.168.17(50295)
PAT Global 192.118.64.25(15776) Local 10.20.168.17(50283)
PAT Global 192.118.64.25(15772) Local 10.20.168.17(50269)
PAT Global 192.118.64.25(15771) Local 10.20.168.17(50268)
PAT Global 192.118.64.25(15770) Local 10.20.168.17(50267)
PAT Global 192.118.64.25(15769) Local 10.20.168.17(50266)
PAT Global 192.118.64.25(15768) Local 10.20.168.17(50258)
PAT Global 192.118.64.25(15767) Local 10.20.168.17(50257)
PAT Global 192.118.64.25(15766) Local 10.20.168.17(50239)
PAT Global 192.118.64.25(15762) Local 10.20.168.17(50231)
PAT Global 192.118.64.25(15761) Local 10.20.168.17(50230)
PAT Global 192.118.64.25(15760) Local 10.20.168.17(50229)
PAT Global 192.118.64.25(15759) Local 10.20.168.17(50228)
PAT Global 192.118.64.25(15758) Local 10.20.168.17(50220)
PAT Global 192.118.64.25(15757) Local 10.20.168.17(50219)
PAT Global 192.118.64.25(15756) Local 10.20.168.17(50201)
PAT Global 192.118.64.25(13453) Local 10.20.168.17(63808)
PAT Global 192.118.64.25(12325) Local 10.20.168.17(60264)
PAT Global 192.118.64.25(9236) Local 10.20.168.17(56730)
PAT Global 192.118.64.254(60725) Local 10.20.2.142(44220)
PAT Global 192.118.64.254(60724) Local 10.20.2.142(35484)
PAT Global 192.118.64.254(60723) Local 10.20.2.142(54202)
PAT Global 192.118.64.254(60722) Local 10.20.2.142(44165)
PAT Global 192.118.64.254(60712) Local 10.20.2.142(49042)
PAT Global 192.118.64.254(60711) Local 10.20.2.142(37050)
PAT Global 192.118.64.254(60707) Local 10.20.2.142(43497)
PAT Global 192.118.64.254(60705) Local 10.20.2.142(48435)
PAT Global 192.118.64.254(60689) Local 10.20.2.142(37279)
PAT Global 192.118.64.254(60687) Local 10.20.2.142(58739)
PAT Global 192.118.64.254(60683) Local 10.20.2.142(57718)
PAT Global 192.118.64.254(60679) Local 10.20.2.142(48691)
PAT Global 192.118.64.254(60626) Local 10.20.2.142(39985)
PAT Global 192.118.64.254(60624) Local 10.20.2.142(34955)
PAT Global 192.118.64.254(60621) Local 10.20.2.142(47069)
PAT Global 192.118.64.254(60620) Local 10.20.2.142(40269)
PAT Global 192.118.64.254(60618) Local 10.20.2.142(41912)
PAT Global 192.118.64.254(60616) Local 10.20.2.142(53963)
PAT Global 192.118.64.254(60568) Local 10.20.2.142(55392)
PAT Global 192.118.64.254(60567) Local 10.20.2.142(58272)
PAT Global 192.118.64.254(60566) Local 10.20.2.142(57089)
PAT Global 192.118.64.254(60565) Local 10.20.2.142(48443)
PAT Global 192.118.64.254(60564) Local 10.20.2.142(40410)
PAT Global 192.118.64.254(60563) Local 10.20.2.142(59388)
PAT Global 192.118.64.254(60096) Local 10.20.2.142(36899)
PAT Global 192.118.64.254(60094) Local 10.20.2.142(41510)
PAT Global 192.118.64.254(60093) Local 10.20.2.142(47320)
PAT Global 192.118.64.254(60091) Local 10.20.2.142(53845)
PAT Global 192.118.64.254(60074) Local 10.20.2.142(43618)
PAT Global 192.118.64.254(60073) Local 10.20.2.142(56750)
PAT Global 192.118.64.254(60071) Local 10.20.2.142(51559)
PAT Global 192.118.64.254(60069) Local 10.20.2.142(38539)
PAT Global 192.118.64.254(60062) Local 10.20.2.142(55866)
PAT Global 192.118.64.254(60060) Local 10.20.2.142(41794)
PAT Global 192.118.64.254(60053) Local 10.20.2.142(41179)
PAT Global 192.118.64.254(60051) Local 10.20.2.142(45151)
PAT Global 192.118.64.254(60015) Local 10.20.2.142(57502)
PAT Global 192.118.64.254(60012) Local 10.20.2.142(56950)
PAT Global 192.118.64.254(60003) Local 10.20.2.142(42474)
PAT Global 192.118.64.254(60001) Local 10.20.2.142(53867)
PAT Global 192.118.64.254(59999) Local 10.20.2.142(50854)
PAT Global 192.118.64.254(59997) Local 10.20.2.142(50096)
PAT Global 192.118.64.254(59891) Local 10.20.2.142(44769)
PAT Global 192.118.64.254(59890) Local 10.20.2.142(36445)
PAT Global 192.118.64.254(59887) Local 10.20.2.142(36065)
PAT Global 192.118.64.254(59883) Local 10.20.2.142(45080)
PAT Global 192.118.64.254(59882) Local 10.20.2.142(43729)
PAT Global 192.118.64.254(59881) Local 10.20.2.142(54565)
PAT Global 192.118.64.254(59592) Local 10.20.2.142(50116)
PAT Global 192.118.64.254(59588) Local 10.20.2.142(59466)
PAT Global 192.118.64.254(59587) Local 10.20.2.142(49488)
PAT Global 192.118.64.254(59584) Local 10.20.2.142(53126)
PAT Global 192.118.64.254(59563) Local 10.20.2.142(52899)
PAT Global 192.118.64.254(59562) Local 10.20.2.142(46938)
PAT Global 192.118.64.254(59558) Local 10.20.2.142(37855)
PAT Global 192.118.64.254(59557) Local 10.20.2.142(40397)
PAT Global 192.118.64.254(59550) Local 10.20.2.142(60394)
PAT Global 192.118.64.254(59548) Local 10.20.2.142(39326)
PAT Global 192.118.64.254(59545) Local 10.20.2.142(40827)
PAT Global 192.118.64.254(59543) Local 10.20.2.142(37845)
PAT Global 192.118.64.254(59473) Local 10.20.2.142(53589)
PAT Global 192.118.64.254(59472) Local 10.20.2.142(40525)
PAT Global 192.118.64.254(59470) Local 10.20.2.142(58406)
PAT Global 192.118.64.254(59469) Local 10.20.2.142(39265)
PAT Global 192.118.64.254(59466) Local 10.20.2.142(52619)
PAT Global 192.118.64.254(59465) Local 10.20.2.142(37318)
PAT Global 192.118.64.254(44841) Local 10.20.137.78(56281)
PAT Global 192.118.64.254(59941) Local 10.21.32.19(51904)
PAT Global 192.118.64.254(59940) Local 10.21.32.19(51903)
PAT Global 192.118.64.254(59936) Local 10.21.32.19(51902)
PAT Global 192.118.64.254(49164) Local 10.21.32.19(9909)
PAT Global 192.118.64.254(19801) Local 10.20.162.31(53046)
PAT Global 192.118.64.254(19800) Local 10.20.162.31(53045)
PAT Global 192.118.64.254(19817) Local 10.20.5.141(60655)
PAT Global 192.118.64.254(19816) Local 10.20.5.141(60654)
PAT Global 192.118.64.254(19814) Local 10.20.5.141(60653)
PAT Global 192.118.64.254(19813) Local 10.20.5.141(60652)
PAT Global 192.118.64.254(19812) Local 10.20.5.141(60651)
PAT Global 192.118.64.254(19808) Local 10.20.5.141(60648)
PAT Global 192.118.64.254(32797) Local 10.20.152.181(64236)
PAT Global 192.118.64.254(19335) Local 10.20.145.11(18921)
PAT Global 192.118.64.254(19484) Local 10.20.153.217(2404)
PAT Global 192.118.64.254(19328) Local 10.20.152.229(55955)
PAT Global 192.118.64.254(2961) Local 10.20.153.57(19907)
PAT Global 192.118.64.254(2960) Local 10.20.153.57(19906)
PAT Global 192.118.64.254(19757) Local 10.20.171.243(64777)
PAT Global 192.118.64.254(18920) Local 10.20.171.243(64637)
PAT Global 192.118.64.254(19200) Local 10.20.152.165(27739)
PAT Global 192.118.64.254(19741) Local 10.20.169.45(58980)
PAT Global 192.118.64.254(19330) Local 10.20.152.22(24333)
PAT Global 192.118.64.254(52500) Local 10.20.147.70(38568)
PAT Global 192.118.64.254(52499) Local 10.20.147.70(38567)
PAT Global 192.118.64.25(25429) Local 10.20.2.93(36385)
PAT Global 192.118.64.254(43770) Local 10.20.152.36(20756)
PAT Global 192.118.64.254(40238) Local 10.20.152.36(20524)
PAT Global 192.118.64.254(29608) Local 10.20.147.112(64859)
PAT Global 192.118.64.254(29607) Local 10.20.147.112(64858)
PAT Global 192.118.64.29(41737) Local 10.20.5.27(42601)
PAT Global 192.118.64.29(41736) Local 10.20.5.27(49940)
PAT Global 192.118.64.29(41733) Local 10.20.5.27(50239)
PAT Global 192.118.64.29(41730) Local 10.20.5.27(21009)
PAT Global 192.118.64.29(41728) Local 10.20.5.27(46598)
PAT Global 192.118.64.29(41727) Local 10.20.5.27(48437)
PAT Global 192.118.64.29(41726) Local 10.20.5.27(24003)
PAT Global 192.118.64.29(41719) Local 10.20.5.27(54568)
PAT Global 192.118.64.29(41717) Local 10.20.5.27(23265)
PAT Global 192.118.64.29(41712) Local 10.20.5.27(21789)
PAT Global 192.118.64.29(41711) Local 10.20.5.27(31140)
PAT Global 192.118.64.29(41710) Local 10.20.5.27(50230)
PAT Global 192.118.64.29(41699) Local 10.20.5.27(59824)
PAT Global 192.118.64.29(41698) Local 10.20.5.27(31390)
PAT Global 192.118.64.29(41695) Local 10.20.5.27(30559)
PAT Global 192.118.64.29(41694) Local 10.20.5.27(45980)
PAT Global 192.118.64.29(41692) Local 10.20.5.27(25064)
PAT Global 192.118.64.29(41691) Local 10.20.5.27(22408)
PAT Global 192.118.64.29(41690) Local 10.20.5.27(20894)
PAT Global 192.118.64.29(41688) Local 10.20.5.27(37984)
PAT Global 192.118.64.29(41687) Local 10.20.5.27(60966)
PAT Global 192.118.64.29(41685) Local 10.20.5.27(44716)
PAT Global 192.118.64.29(41684) Local 10.20.5.27(17482)
PAT Global 192.118.64.29(41683) Local 10.20.5.27(51781)
PAT Global 192.118.64.29(41682) Local 10.20.5.27(40295)
PAT Global 192.118.64.29(41681) Local 10.20.5.27(35828)
PAT Global 192.118.64.29(41679) Local 10.20.5.27(42823)
PAT Global 192.118.64.29(41678) Local 10.20.5.27(50224)
PAT Global 192.118.64.29(41674) Local 10.20.5.27(39926)
PAT Global 192.118.64.29(41673) Local 10.20.5.27(48617)
PAT Global 192.118.64.29(41667) Local 10.20.5.27(41523)
PAT Global 192.118.64.29(41666) Local 10.20.5.27(18380)
PAT Global 192.118.64.29(41660) Local 10.20.5.27(18875)
PAT Global 192.118.64.29(41658) Local 10.20.5.27(59260)
PAT Global 192.118.64.29(41656) Local 10.20.5.27(50218)
PAT Global 192.118.64.29(41655) Local 10.20.5.27(47237)
PAT Global 192.118.64.29(41654) Local 10.20.5.27(20836)
PAT Global 192.118.64.29(41653) Local 10.20.5.27(20652)
PAT Global 192.118.64.29(41652) Local 10.20.5.27(19352)
PAT Global 192.118.64.29(41650) Local 10.20.5.27(57884)
PAT Global 192.118.64.29(41646) Local 10.20.5.27(52651)
PAT Global 192.118.64.29(41645) Local 10.20.5.27(33602)
PAT Global 192.118.64.29(41643) Local 10.20.5.27(24907)
PAT Global 192.118.64.29(41641) Local 10.20.5.27(42440)
PAT Global 192.118.64.29(41640) Local 10.20.5.27(32943)
PAT Global 192.118.64.29(41639) Local 10.20.5.27(21766)
PAT Global 192.118.64.29(41638) Local 10.20.5.27(22091)
PAT Global 192.118.64.29(41637) Local 10.20.5.27(56198)
PAT Global 192.118.64.29(41635) Local 10.20.5.27(30385)
PAT Global 192.118.64.29(41634) Local 10.20.5.27(28680)
PAT Global 192.118.64.29(41632) Local 10.20.5.27(45206)
PAT Global 192.118.64.29(41631) Local 10.20.5.27(18996)
PAT Global 192.118.64.29(41630) Local 10.20.5.27(30498)
PAT Global 192.118.64.29(41629) Local 10.20.5.27(21762)
PAT Global 192.118.64.29(41628) Local 10.20.5.27(21761)
PAT Global 192.118.64.29(41627) Local 10.20.5.27(42895)
PAT Global 192.118.64.29(41626) Local 10.20.5.27(38742)
PAT Global 192.118.64.29(41625) Local 10.20.5.27(17210)
PAT Global 192.118.64.29(41624) Local 10.20.5.27(50711)
PAT Global 192.118.64.29(41623) Local 10.20.5.27(28304)
PAT Global 192.118.64.29(41622) Local 10.20.5.27(31853)
PAT Global 192.118.64.29(41621) Local 10.20.5.27(30445)
PAT Global 192.118.64.29(41620) Local 10.20.5.27(37302)
PAT Global 192.118.64.29(41619) Local 10.20.5.27(52503)
PAT Global 192.118.64.29(41618) Local 10.20.5.27(28556)
PAT Global 192.118.64.29(41614) Local 10.20.5.27(23089)
PAT Global 192.118.64.29(41613) Local 10.20.5.27(46511)
PAT Global 192.118.64.29(41611) Local 10.20.5.27(52710)
PAT Global 192.118.64.29(41610) Local 10.20.5.27(50199)
PAT Global 192.118.64.29(41608) Local 10.20.5.27(47986)
PAT Global 192.118.64.29(41607) Local 10.20.5.27(46659)
PAT Global 192.118.64.29(41606) Local 10.20.5.27(17142)
PAT Global 192.118.64.29(41605) Local 10.20.5.27(50141)
PAT Global 192.118.64.29(41604) Local 10.20.5.27(33451)
PAT Global 192.118.64.29(41603) Local 10.20.5.27(37977)
PAT Global 192.118.64.29(41602) Local 10.20.5.27(54506)
PAT Global 192.118.64.29(41601) Local 10.20.5.27(25360)
PAT Global 192.118.64.29(41600) Local 10.20.5.27(54325)
PAT Global 192.118.64.29(41599) Local 10.20.5.27(50792)
PAT Global 192.118.64.29(41598) Local 10.20.5.27(29431)
PAT Global 192.118.64.29(41597) Local 10.20.5.27(39571)
PAT Global 192.118.64.29(41596) Local 10.20.5.27(60909)
PAT Global 192.118.64.29(41595) Local 10.20.5.27(17058)
PAT Global 192.118.64.29(41594) Local 10.20.5.27(37380)
PAT Global 192.118.64.29(41593) Local 10.20.5.27(53162)
PAT Global 192.118.64.29(41592) Local 10.20.5.27(41302)
PAT Global 192.118.64.29(41591) Local 10.20.5.27(27847)
PAT Global 192.118.64.29(41588) Local 10.20.5.27(51638)
PAT Global 192.118.64.29(41587) Local 10.20.5.27(24338)
PAT Global 192.118.64.29(41586) Local 10.20.5.27(49915)
PAT Global 192.118.64.29(41584) Local 10

Similar Messages

  • LMS 4.2.3 Server high CPU Utilization

    Hi All,
    We are observing high CPU utilization on the lms server. tomcat is the process eating more than 1GB of the memory i checked from the task manager.
    Server details:
    device license : 100
    windows server 2k8 R2, with 8gb physical memory.
    anybody suggest what might be causing the issue.?? because of this performance reports were affected.
    Regards,
    Channa

    Hi Channa,
    log into dbreader using the following::
    http://servername : 1741/dbreader/dbreader.html
    or
    https:// servername : 443/dbreader/dbreader.html
    user Id is DBA
    Database Name is upm
    password :: user defined (by default password is c2ky2k)
    1.       Here is the query to get the pollerwise managed MIBObjects:
    "select count (*), PollerName from Poller_Details_Table a,Poller_Definition_Table b where a.PollerId = b.PollerId and b.Poller_State NOT IN (1) Group by b.PollerName;"
    2.       Here is the query to get the total mibobject count for the active pollers
    “select count (*) from Poller_Details_Table a,Poller_Definition_Table b where a.PollerId =
    b.PollerId and b.Poller_State NOT IN (1);”
    Hope it will help
    Thanks-
    Afroz
    ***Ratings Encourages Contributors ***

  • Desktop Window Manager high CPU utilization

    I have several Windows 2012 servers that are showing high CPU utilization (70% or higher) coming from the Desktop Window Manager.  I do not have the Desktop Experience feature installed on these machines.  The interesting thing is that the process
    for dwm.exe does not show up as a service that I can stop or restart.  I've read through the various posts about re-registering dmw.exe so that the service shows up again, but nothing has worked.  Since these are application and file servers with
    no need for regular desktop use, I don't really need any fancy desktop graphics or performance.  I have the Advanced Performance Options set to 'Background services'.  Can anyone tell me how to stop dwm.exe or at least reduce it's CPU footprint?
    Thanks,
    Joe

    Hi Joe,
    Based on my research, On Windows 8 and Windows Server 2012, DWM is used at all times and cannot be disabled.
    For more detailed information, please refer to this article:
    Desktop Window Manager is always on:
    To troubleshoot the high usage of CPU, I would like to recommend to follow this article to collect and analyse the relevant log files and dump files:
    Troubleshooting High CPU performance issues - Part 1
    If you want to analyse the dump file, I also recommend you can open case and contact Microsoft support.
    I hope this helps.

  • NSAPI plugin has high CPU utilization on Sunone web server 6.0 SP5

    Hi,
    I am running WL 6.1 SP3 with pluginProxy SP03 on Sunone web server 6.0SP5 on Solaris.
    Seeing very high CPU utilization with 3 threads running wl_proxy (about 33% each).
    Any latest NSAPI pluginproxy patch I can use to fix this?
    Walter

    I'm having the same problems as all the above posts. I run a colloborative tool which uses IPlanet as a directory server and I receive the Event ID:25 Source: WebServer 6.0 error as well as Event ID:0 Source:https-admnserv6.0 which gives "the local computer may not have the necessary registry information or message DLL files to display messages from a remote computer". I have 3 servers built and all exhibit the same errors.

  • Very high cpu utilization with mq broker

    Hi all,
    I see a very high cpu utilization (400% on 8 cpu server) when I connect consumers to OpenQ. It increase close to 100% for every consumer I add. Slowly, the consumer comes to a halt, as the producers are sending messages at a good rate too.
    Environment Setup
    Glassfish version 2.1
    com.sun.messaging.jmq Version Information Product Compatibility Version: 4.3 Protocol Version: 4.3 Target JMS API Version: 1.1
    Cluster set up using persistent storage. snippet from broker log.
    Java Runtime: 1.6.0_14 Sun Microsystems Inc. /home/user/foundation/jdk-1.6/jre [06/Apr/2011:12:48:44 EDT] IMQ_HOME=/home/user/foundation/sges/imq [06/Apr/2011:12:48:44 EDT] IMQ_VARHOME=/home/user/foundation/installation/node-agent-server1/server1/imq [06/Apr/2011:12:48:44 EDT] Linux 2.6.18-164.10.1.el5xen i386 server1 (8 cpu) user [06/Apr/2011:12:48:44 EDT] Java Heap Size: max=394432k, current=193920k [06/Apr/2011:12:48:44 EDT] Arguments: -javahome /home/user/foundation/jdk-1.6 -Dimq.autocreate.queue=false -Dimq.autocreate.topic=false -Dimq.cluster.masterbroker=mq://server1:37676/ -Dimq.cluster.brokerlist=mq://server1:37676/,mq://server2:37676/ -Dimq.cluster.nowaitForMasterBroker=true -varhome /home/user/foundation/installation/node-agent-server1/server1/imq -startRmiRegistry -rmiRegistryPort 37776 -Dimq.imqcmd.user=admin -passfile /tmp/asmq5711749746025968663.tmp -save -name clusterservercom -port 37676 -bgnd -silent [06/Apr/2011:12:48:44 EDT] [B1004]: Starting the portmapper service using tcp [ 37676, 50, * ] with min threads 1 and max threads of 1 [06/Apr/2011:12:48:45 EDT] [B1060]: Loading persistent data...
    I followed step in http://middlewaremagic.com/weblogic/?p=4884 to narrow it down to Threads that was causing high cpu. Both were around 94%.
    Following is the stack for those threads.
    "Thread-jms[224]" prio=10 tid=0xd635f400 nid=0x5665 runnable [0xd18fe000] java.lang.Thread.State: RUNNABLE at com.sun.messaging.jmq.jmsserver.data.TransactionList.isConsumedInTransaction(TransactionList.java:697) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:918) - locked <0xf3d35730> (a java.util.Collections$SynchronizedMap) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:810) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.destroyConsumer(ConsumerHandler.java:577) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.handle(ConsumerHandler.java:422) at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1489) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:644) at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170) at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - None
    "Thread-jms[214]" prio=10 tid=0xd56c8000 nid=0x566c waiting for monitor entry [0xd2838000] java.lang.Thread.State: BLOCKED (on object monitor) at com.sun.messaging.jmq.jmsserver.data.TransactionInformation.isConsumedMessage(TransactionList.java:2544) - locked <0xdbeeb538> (a com.sun.messaging.jmq.jmsserver.data.TransactionInformation) at com.sun.messaging.jmq.jmsserver.data.TransactionList.isConsumedInTransaction(TransactionList.java:697) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:918) - locked <0xe4c9abf0> (a java.util.Collections$SynchronizedMap) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:810) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.destroyConsumer(ConsumerHandler.java:577) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.handle(ConsumerHandler.java:422) at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1489) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:644) at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170) at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - None
    "Thread-jms[213]" prio=10 tid=0xd65be800 nid=0x5670 runnable [0xd1a28000] java.lang.Thread.State: RUNNABLE at com.sun.messaging.jmq.jmsserver.data.TransactionList.isConsumedInTransaction(TransactionList.java:697) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:918) - locked <0xe4c4bad8> (a java.util.Collections$SynchronizedMap) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:810) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.destroyConsumer(ConsumerHandler.java:577) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.handle(ConsumerHandler.java:422) at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1489) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:644) at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170) at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - None
    Any ideas will be appreciated.
    --

    Thanks ak, for the response.
    Yes, the messages are consumed in transactions. I set imq.txn.reapLimit=200 in Start Arguments in jvm configuration.
    I verified that it is being set in the log.txt file for the broker:
    -Dimq.autocreate.queue=false -Dimq.autocreate.topic=false -Dimq.txn.reapLimit=250
    It did not make any difference. Do I need to set this property somewhere else ?
    As far as upgrading MQ is concerned, I am using glassfish 2.1. And I think MQ 4.3 is packaged with it. Can you suggest a safe way to upgrade to OpenMQ 4.5 in a running environment. I can bring down the cluster temporarily. Can I just change the jar file somwhere to use MQ4.5 ?
    Here is the snippet of the consumer code :
    I create Connection in @postConstruct and close it in @preDestroy, so that I don't have to do it everytime.
    private ResultMessage[] doRetrieve(String username, String password, String jndiDestination, String filter, int maxMessages, long timeout, RetrieveType type)
    throws InvalidCredentialsException, InvalidFilterException, ConsumerException {
    // Resources
    Session session = null;
    try {
    if (log.isTraceEnabled()) log.trace("Creating transacted session with JMS broker.");
    session = connection.createSession(true, Session.SESSION_TRANSACTED);
    // Locate bound destination and create consumer
    if (log.isTraceEnabled()) log.trace("Searching for named destination: " + jndiDestination);
    Destination destination = (Destination) ic.lookup(jndiDestination);
    if (log.isTraceEnabled()) log.trace("Creating consumer for named destination " + jndiDestination);
    MessageConsumer consumer = (filter == null || filter.trim().length() == 0) ? session.createConsumer(destination) : session.createConsumer(destination, filter);
    if (log.isTraceEnabled()) log.trace("Starting JMS connection.");
    connection.start();
    // Consume messages
    if (log.isDebugEnabled()) log.trace("Creating retrieval containers.");
    List<ResultMessage> processedMessages = new ArrayList<ResultMessage>(maxMessages);
    BytesMessage jmsMessage = null;
    for (int i = 0 ; i < maxMessages ; i++) {
    // Attempt message retrieve
    if (log.isTraceEnabled()) log.trace("Attempting retrieval: " + i);
    switch (type) {
    case BLOCKING :
    jmsMessage = (BytesMessage) consumer.receive();
    break;
    case IMMEDIATE :
    jmsMessage = (BytesMessage) consumer.receiveNoWait();
    break;
    case TIMED :
    jmsMessage = (BytesMessage) consumer.receive(timeout);
    break;
    // Process retrieved message
    if (jmsMessage != null) {
    if (log.isTraceEnabled()) log.trace("Message retrieved\n" + jmsMessage);
    // Extract message
    if (log.isTraceEnabled()) log.trace("Extracting result message container from JMS message.");
    byte[] extracted = new byte[(int) jmsMessage.getBodyLength()];
    jmsMessage.readBytes(extracted);
    // Decompress message
    if (jmsMessage.propertyExists(COMPRESSED_HEADER) && jmsMessage.getBooleanProperty(COMPRESSED_HEADER)) {
    if (log.isTraceEnabled()) log.trace("Decompressing message.");
    extracted = decompress(extracted);
    // Done processing message
    if (log.isTraceEnabled()) log.trace("Message added to retrieval container.");
    String signature = jmsMessage.getStringProperty(DIGITAL_SIGNATURE);
    processedMessages.add(new ResultMessage(extracted, signature));
    } else
    if (log.isTraceEnabled()) log.trace("No message was available.");
    // Package return container
    if (log.isTraceEnabled()) log.trace("Packing retrieved messages to return.");
    ResultMessage[] collectorMessages = new ResultMessage[processedMessages.size()];
    for (int i = 0 ; i < collectorMessages.length ; i++)
    collectorMessages[i] = processedMessages.get(i);
    if (log.isTraceEnabled()) log.trace("Returning " + collectorMessages.length + " messages.");
    return collectorMessages;
    } catch (NamingException ex) {
    sessionContext.setRollbackOnly();
    log.error("Unable to locate named queue: " + jndiDestination, ex);
    throw new ConsumerException("Unable to locate named queue: " + jndiDestination, ex);
    } catch (InvalidSelectorException ex) {
    sessionContext.setRollbackOnly();
    log.error("Invalid filter: " + filter, ex);
    throw new InvalidFilterException("Invalid filter: " + filter, ex);
    } catch (IOException ex) {
    sessionContext.setRollbackOnly();
    log.error("Message decompression failed.", ex);
    throw new ConsumerException("Message decompression failed.", ex);
    } catch (GeneralSecurityException ex) {
    sessionContext.setRollbackOnly();
    log.error("Message decryption failed.", ex);
    throw new ConsumerException("Message decryption failed.", ex);
    } catch (JMSException ex) {
    sessionContext.setRollbackOnly();
    log.error("Unable to consumer messages.", ex);
    throw new ConsumerException("Unable to consume messages.", ex);
    } catch (Throwable ex) {
    sessionContext.setRollbackOnly();
    log.error("Unexpected error.", ex);
    throw new ConsumerException("Unexpected error.", ex);
    } finally {
    try {
    if (session != null) session.close();
    } catch (JMSException ex) {
    log.error("Unexpected error.", ex);
    Thanks for your help.
    Edited by: vineet on Apr 7, 2011 10:06 AM

  • EEM applet that triggers on high CPU utilization

    Hi Folks,
    I am trying to create an eem applet which triggers on high cpu utilization (detected by erm).   The applet should then tftp the output from "show proc cpu sorted" to a tftp server.   
    I am trying to configure this on a 1841 running 124-24.T3 code
    This is my config:
    resource policy
      policy HighGlobalCPU global
       system
        cpu total
         critical rising 5 falling 2 interval 10
        cpu process
         critical rising 5 falling 2 interval 10
    ! I'm not sure whether it is correct to monitor 'cpu total' or 'cpu process'.   The rising thresholds are deliberately low to maker testing easier
    event manager applet ReportHighCPU
    event resource policy "HighGlobalCPU"
    action 1.0 cli command "show process cpu sorted 5sec | redirect tftp://192.168.1.1/highCPU$_resource_time_sent.txt"
    action 2.0 syslog priority debugging msg "high cpu event detected, output tftp sent"
    The problem is that I can't seem to trigger the applet.    I have generated enough traffic to push the cpu utilization to over 30% (according to 'show proc cpu'), but the applet does not appear to trigger (no syslog messages appear, and my syslog server does not receive anything).
    If anyone can tell me what I've done wrong here I would be very grateful!
    Thanks,
    Darragh

    I am just replying off the top of my head but I believe you
    need to also add to your conf the line
    user global HighGlobalCPU

  • CB21AG High CPU Utilization

    We have a problem with CB21AG cards causing high CPU utilization on WinXP. Task manager shows the CPU pegged at 100%, but the individual processes don't add up to 100%. IE, there are "missing" CPU cycles. Using Process Monitor from SysInternals, we see that NDIS (Windows network wrapper) is creating numerous DPCs and causing the CPU usage. Shutting down the wireless card fixes the problem. It's an LWAPP environment (WiSM 4.0.217), with various versions of the client drivers up to ADU 3.6.
    Does anyone know anything about this?

    It'd be hard to say anything for certain without seeing all the test stuff ... but it sounds like old or corrupt drivers / utilities.
    There are some Microsoft-side patches / updates that may be useful as well.
    Try reloading the (and / or updating) the drivers & utilities. If you're using Zero Wireless Config, try (at least for experimentation) the Cisco utilities (ADU) or vice-versa. It might narrow down which specific software modules are involved.
    IF you have a spare card, it might also be worth a shot ... there could be a bad software component in EPROM that's causing the problem.
    I believe some of the driver/utility updates include updated firmware loads for the NIC too.
    Good Luck
    Scott

  • WAAS experiencing high CPU utilization

    We are monitoring WAAS devices for CPU utilization in our Network.Currently we have set the threshold for 70%. At this threshold we see a large number of alerts from WAAS crossing 70% CPU utilization. I guess 70% CPU utilization is normal for WAAS. Am I right???

    Hi Daniel,
    Yes, during the peak hours sometimes the CPU shoots even upto 95% and then in next 5 min comes down to normal below 70%.
    Since our threshold is 70%, we get a lot of inactionable(because it becomes normal in 5-10 miinutes only) alert.I was wondering if we could change the threshold.
    One of the Cisco Tac Engineer replied to the above question :
    That is true. It is normal to have a high CPU utilization in normal Operation as we mentioned earlier it runs on underlying Linux kernel and linux does not use Page file rather it uses Maximum RAM that it could .
    Regards,
    Mohit

  • SCCM 2012 Agent and high CPU utilization.

    We have numerous Windows workstations and servers running with very high CPU utilization. Services are slow to start and login can take an hour. The service running with high CPU is svchost.exe, we determined that it is Windows Management Instrumentation
    that is causing high CPU in svchost.exe.
    If we stop or uninstall the SCCM 2012 Agent, everything calms down on the computer.
    Any ideas as to way this would be?

    Same issue seen on a clients and KB2617858 resolves it. I am deploying using the App model no problem with x86 and x64 hotfixes with requisite OS requirements. Is there a way to configure to only apply to those that it applies to...if that makes sense. I
    ask because my B&C x64 W7Sp1 image does not require it (I have not included it) whereas other non-B&C do - what's the condition or applicability (or non-applicability) if not as listed on the KB..! If I run it one W7 machine it says it doesn't apply
    and isn't already, whereas another it installs..!
    http://support.microsoft.com/kb/2705357:
    To apply this hotfix, you must be running one of the following operating systems:
    Windows 7
    Windows 7 Service Pack 1 (SP1)
    Windows Server 2008 R2
    Windows Server 2008 R2 Service Pack 1 (SP1)
    ..obviously, if a client has the issue it applies :)
    Donald Rumsfeld's 'known unknowns' comes to mind here. Sorry.

  • High CPU utilization on 2960 switch

    Hi
    I have a 2960 switch connected in my network. It is showing high CPU utilization upto 80-90%. When I checked I found that the below processes are taking the highest utilization. The image in the switch is LAN base. Can someone please advice on why I am having high utilization on the switch for the below processes and how can I reduce it.
    14.69% 14.98% 15.00%   0 Hulc LED Process
    14.69% 11.49% 13.97%   0 IP Input
    29.07% 28.44% 30.06%   0 DHCPD Receive

    Duplicate post. 
    Go HERE.

  • High CPU utilization with javascript

    Has anyone noticed how Safari 10.4.4 has high CPU utilization (e.g. >60%) when javascript is enabled, particularly for certain websites? Opening FoxNews.com and a few Wired.com pages in separate tabs sends my Powerbook fans screaming. Disabling javascript brings utilization down to under 2%.
    Any suggestions on how to fix this, or do I have to live with it? I prefer not to permanently disable javascript as a number of websites I frequent depend upon it, without consuming CPU.
    Thanks,
    Ira

    Hi,
    I agree that it's a function of the javascript code itself on the webpage, and not with the browser. It's possible to even write infinite loops in Javascript which can practically hang a web browser due to the high percentage of CPU cycles being consumed. I only knowingly encountered such a site once, when I was at a customer site with my PowerBook running on battery power. I unknowingly navigated to a site which apparently had some Javascript of some other executable code, which had the result of running my battery from about 95% charge to about 60% in about 10 minutes!
    The only way to avoid this is to avoid the sites that cause this kind of problem, or to disable Javascript when visiting these sites. And if possible, send a complaint to the webmaster of the site. He/she might not be aware of this problem.
    Ken

  • High CPU Utilization by J2EE engine

    Dear team,
    I want to find the tread causing high CPU utilization within the "jlaunch" process. As stated in SAP note: 743204. I ran the command "tps -a <pid> -a" in the development box and it it running fine. But the same command in the production portal is giving us the following error:
    jueppci:/#/usr/sap/tps -a                                                                               
    Initialize measurement (10 sec) ...Memory fault(coredump)    
    I did a strings command om the core and  I got
    jueppci:/#strings core                                       
    libdl.so                                                    
    Why is tps not running properly ?

    Hello,
    Thanks Russell. It is HP-UX 11.31 (11i v3). We have opened a Very High Message with SAP. SAP AG and HP are working with us to solve this issue. We will be applying some patches and doing a lot of Java parameter changes !
    I'll update the solution once the system is stable and the case with SAP is closed.

  • 3G High CPU utilization when waking

    Recently gave my iPhone 3G to my wife, restored it to a new phone, then synced it with her information, music, applications, etc. She previously had used an iPod touch, and basically was trying to upgrade her to an iPhone.
    The phone worked fine when I had it. I only had a short time with this specific phone as it was replaced under Apple Care about a week and a half before turning it over.
    Now it pretty consistently is unresponsive when trying to wake it. By bringing up the System Activity Monitor App as soon as possible after powering it up, and leaving that app active when putting it to sleep I can see that the CPU gets slammed for a while during initial startup and has a significant period of very high CPU when waking. At this point I believe the cause of the unresponsive behavior is that the CPU is maxed out doing something.
    I've compared the running processes to an iPhone 3Gs and they were identical except the 3G was missing the MobileMusicPlaye until I brought up the iPod on that phone.
    There are 2 things about the initial setup of this phone for my wife that are causing me some concern;
    1) When first connected to iTunes after the Factory Reset I was prompted to restore an older backup than the iPod Touch one I took right before the swap. I didn't realize it at the time and accepted that restore.
    2) I was prompted to upgrade and followed through with an upgrade to 3.1.2 after the Factory Reset even though the phone was at 3.1.2 before the swap.
    At this point I'm thinking about doing another Factory reset and set it up by sync only (no restore) but not looking forward to the time investment that will take.
    Any ideas on where the high CPU utilization is coming from on wake? Is that a reasonable theory that the high CPU is causing it to be unresponsive when first woken up.
    Any other insight from others that have been through this?

    I ended up restoring the 3G phone to Factory settings and then sync'ing the desired information / applications onto it (did not restore the previous backup). The behavior is improved but this phone does seem to get bogged down when waking (observing high CPU utilization when monitoring with System Activity Monitor and experiencing sluggish / jerky response to user actions with no applications or just Mail running). The periods of non-responsiveness are not as long or as severe at this point, but still noticeable.
    I'm at a loss since under the conditions I'm observing this there is nothing but Apple software running on the device (behavior is present with or without SAM showing me the CPU utilization). I'm a little suspicious that it might have something to do with re-establishing the WiFi connection, but it seems to continue for a bit after the WiFi icon appears in the status bar.
    I'm probably going to make a genius appointment to see if they have any other ideas.

  • High CPU Utilization on Lync Mediation Servers -

    All,
    We are experiencing an issue for last couple of weeks where we are seeing very high CPU utilization on our Lync Mediation Servers (connected
    directly to SIP gateway). It is resulting in a high Jitter value and so the poor call quality.
    The CPU utilization is normal on mediation boxes on our other Lync hubs regardless of the number of inbound/outbound calls
    but on new Lync hub, as soon as the call volume (inbound/outbound) reaches over ~10-15 calls, CPU peaks nearly 80%-90% utilization. To reduce the call volume, we have routed our outbound calls to different hub.
    To resolve this we have already taken following troubleshooting actions:
    Increase CPU Cores from 4 to 8 on original Mediation VM  (The mediation boxes in other hubs have 4 CPU Cores and there is no issue)
    Copied known good Mediation VM and replaced a mediation box on new Lync hub
    Created new VM and deployed into Mediation Pool
    Monitoring of HVH’s showed no resource allocation issue
    No indication on Lync Logs or Monitoring reports as to the root cause of the issue 
    Raised this with our SIP suppliers to compare SIP configuration with all our SIPs and they came back with no differences. 
    Unfortunately, after all of the above actions, we have still seeing a high CPU utilization. 
    Can anyone suggest something which helps us to resolve this issue?
    Any assistance appreciated
    Cheers,
    Hemat

    Anti-virus exclusion list/exceptions properly configured on the affected Lync Mediation Servers? Using dynamic instead of fixed-size virtual disks? Is the host hypervisor on the official supported list (see
    Windows Server Virtualization Validation Program)?
    Also do check out the recently updated guide:
    Planning a Lync Server 2013 Deployment on Virtual Servers
    Thanks / rgds,
    TechNet/MSDN Forum Moderator - http://www.leedesmond.com

  • High CPU utilization on CSS 11501 version sg0750303

    Hi everyone,
    I have the problem about High CPU utilization on CSS 11501 version sg0750303.
    Our customer has used one pair of CSS 11501 (active-standby).
    As a matter of convenience, called "Old CSS" after here in this post.
    However traffic via Old CSS had been increasing so customer decided to add one more
    pair (active-standby) of CSS to separate traffic.
    Yesterday we installed new two CSS 11501 version sg0750303 (active-standby).
    As a matter of convenience, called "New CSS" after here in this post.
    Today, active CSS 11501 and standby CSS 11501 which were installed yesterday (New CSSs)
    indicates High CPU utilization.
    Active CSS 11501:
    Peak CPU utilization: about 85%
    Average CPU Utilization: about 60%
    Standby CSS 11501:
    Peak CPU utilization: about 40%
    Average CPU Utilization: unknown
    I do not understand why CPU utilization of both New CSSs become high.
    The traffic pass through New CSS less than Old CSS, because the traffic is separated into
    Old CSS and New CSS.
    And CSS's configuration parameters (service, content, access-list) also less than Old CSS,
    because real servers are also separated into Old CSS and New CSS.
    Old CSS indicated average of CPU utilization about 20% before installing New CSSs yesterday,
    in spite of all traffic pass through Old CSS only.
    I wrote "New CSS remains High CPU utilization", however end users do not feel the
    performance issue (e.g., performance delay, communication failure and so on) and
    the traffic pass through New CSS normally.
    So I have the question "CSS 11501 sg0750303 remains High CPU utilization on normal situation ?"
    And customer uses MTRG to poll SNMP for Old CSSs and New CSSs.
    So I have the question "CSS 11501 sg0750303 become High CPU utilization in case of receiving
    SNMP polling ?".
    Or if this situation is abnormal we need to start investigation.
    Would you please let me know how do we investigate this situation.
    I found the DDTS CSCek57080 "Performance issue using arrowpoint-cookie with ASR".
    Release note of this DDTS says that
    A customer was using a CSS pair configuration where arrowpoint-cookie
    is being used along with a redundant-index on many content rules. When
    the flow rate increased to a few hundred flows/sec, the peer message
    queue of the CSS receiving ASR related message began to fill up.
    When the peer message queue became over subscribed, the CPU increased
    and the CSS became unstable.
    New CSSs have configured redunrant-index on two content rules, and end users do not feel the
    performance issue (e.g., performance delay, communication failure and so on) and
    the traffic pass through New CSS normally.
    So I think this DDTS does not related to this case.
    Your information would be greatly appreciated.
    Best regards,

    Gilles,
    Thank you very much for your cooperation.
    I got the capture you instructed us.
    The following are additional information from our customer.
    At time user traffic path through the active CSS, active CSS indicates;
    CPU utilization always range of 30% - 40%
    Peak CPU utilization about 60% - 80%
    At time there is no user traffic pass through active CSS, active CSS indicates;
    CPU utilization always range of 0% - 5%
    Attached files are named "Active CSS.log" and "Standby CSS.log".
    "Active CSS.log" is captured on active CSS and "Standby CSS.log" is captured on
    standby CSS.
    I found the following process is using resource by looking the output of
    "shell 1 1 spyReport" command.
    On active CSS,
    tFlowMgrPktR 8ba24070 50 26% ( 1469) 20% ( 26)
    On standby CSS,
    fmPeerMsgTas 8a511510 50 16% ( 176) 10% ( 7)
    Your comment would be greatly appreciated.
    Best regards,

Maybe you are looking for

  • Adobe Xi 11.0.10 not printing saved pdfs

    I have Windows 7 Home Premium 64 bit.  Adobe Reader XI was automatically updated to the Dec 2014 version 11.0.10 MUI. Since then I am unable to print any newly saved pdfs nor any of my old pdfs that I have been printing for years.  I AM able to print

  • Rootca  not authenticated by iphone wireless

    I have manually installed rootca certificate on my iphone , but when I try to connect to wireless again it ask me for new certificate. Looks like it is not interception rootca certificates. any help appreciated,

  • Mix firewire 800 & 400 hard drives

    I am getting a new 21.5". I now have a 20" (firewire 400). I have a G-RAID2 with 2 800 and one 400 firewire ports. I also have a G-Drive 400 which I use for Time Machine. On the new iMac, I will connect the G-RAID2 with a 800 cable. But then, should

  • My new wireless keyboard is intermittently losing connection.

    I broke a key on my original iMac wireless keyboard, so I got a new one. Ever since I got it a month ago, however, it will sometimes disconnect and the reconnect seconds later multiple times. It's really annoying, prohibiting me from typing and will

  • XML Data Provider - Information

    Hi! I am using the web item "Data Provider - Information" in the WAD to get a query result in XML. When i choose view source in the explorer i can see the XML generated. My problem is that this generated XML generates one "XML set" for the characteri