Thanks for think, but I don't understand the outputs, the memory is low on the ADSL tool, see below for the CPU info:

User Access Verification

pix# show xlate count

526 in use, 2023 most used

vogate# show processes cpu-hog

^

pix# show processes cpu-hog

MAXHOG NUMHOG LASTHOG Process

-------------- --------------- --------------- ---------

810 43 110 Dispatch Unit

320 873 160 tmatch compile thread

1870 7 110 emweb/https

170 12764 160 snmp

pix# sh int e1

Interface Ethernet1 "inside", is up, line protocol is up

Hardware is i82559, BW 100 Mbps

Full-Duplex(Full-duplex), 100 Mbps(100 Mbps)

MAC address 0004.9ad0.d611, MTU 1500

IP address 192.168.10.50, subnet mask 255.255.0.0

5169231618 packets input, 746373881005 bytes, 0 no buffer

Received 4472764 broadcasts, 0 runts, 0 giants

45207 input errors, 0 CRC, 0 frame, 45207 overrun, 0 ignored, 0 abort

0 L2 decode drops

3346711203 packets output, 810671972009 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 babbles, 0 late collisions, 0 deferred

0 lost carrier, 0 no carrier

input queue (curr/max blocks): hardware (128/128) software (80/269)

output queue (curr/max blocks): hardware (0/89) software (0/1)

Traffic Statistics for "inside":

5170627577 packets input, 671569112347 bytes

3346742625 packets output, 738364163374 bytes

3373483364 packets dropped

vogate#

Try rulling out physical connections problems as there seem to be errors on interfaces.

" 45207 input errors, 0 CRC, 0 frame, 45207 overrun, 0 ignored, 0 abort " this could contribute to high cpu but there may be other reasons.

check physical interfaces

" show interfaces " note counters

if there are erros you many want to watch and note if counters increment or clear cunters.

e.g

pix#config t

pix(config)#clear interface

then check counters again.

if interfaces speed are hard coded to 100/full make sure what they connect to is also 100/full etc..

Nothing has been changed on the Pix for a long time, and it hasn't been rebooted for a few weeks. Could a reboot just be a good idea?

you could try that, however, something must be causing high cpu and it is suspected it may go back to high CPU again after reboot. You may try rebooting but be prepare to investigate fruther with the link I provided to seek the cause of high cpu if it does occur again.