epic9x's questions

I've been looking at using process accounting for keeping track of various users and sites running scripts that are problematic in our environment instead of trying to do something like scraping top at regular intervals.

The one that isn't particularly clear is which fields really denotes the cpu seconds/minutes used. The manual pages I have read say the 'cpu' column is for seconds burned, however there is alo the 'cp' column displayed with -m - and they can show different totals. For example:

When I use the -m flag, I get

 $sa -m | grep username
 username 14944      65.53re      29.90cp     5308k

When I use the -u flag and total up the column for 'cpu', I get the following:

 sa -u |grep username|awk 'BEGIN{TOTAL=0}{TOTAL=TOTAL+$2}END{print TOTAL}'
 1032.86

Can anybody help me understand the difference between the 'cp' and 'cpu' columns in these two different modes?

Thanks!

I've got an aging (ancient?) PIX in front of a website that I need to move, and in order to do that I need to be ready to remove the IP serving that site from the PIX so that the main switches further up our network don't end up sending to the wrong machine.

As far as I can see, the IPs are all setup as static routes that are NAT'ed to IPs serving specific sites and servers behind the PIX (e.g. site serves on public IP 100.100.100.7 is natted to say 192.168.0.46.

As far as I can see form the docs, I should just remove the static route. I also read that running 'clear xlate' afterwards - but i'm not exactly sure what that does. End goal is to make sure I don't end out broadcasting an IP in two places (no VLANs not in place/not an option at this time, though I wish they were).

Realish example with IPs anonymized:

Here's the output from 'show static'

static (inside,outside) 100.100.100.7 192.168.0.46 netmask 255.255.255.255 0 0
static (inside,outside) 100.100.100.6 192.168.0.47 netmask 255.255.255.255 0 0
static (inside,outside) 100.100.100.4 192.168.0.48 netmask 255.255.255.255 0 0
static (inside,outside) 100.100.100.3 192.168.0.49 netmask 255.255.255.255 0 0
static (inside,outside) 100.100.100.1 192.168.0.201 netmask 255.255.255.255 0 0
static (inside,outside) 100.100.100.5 192.168.0.107 netmask 255.255.255.255 0 0
static (inside,outside) 100.100.100.2 192.168.0.202 netmask 255.255.255.255 0 0

Here's the output from 'show xlate':

7 in use, 7 most used
Global 100.100.100.1 Local 192.168.0.201 static
Global 100.100.100.2 Local 192.168.0.202 static
Global 100.100.100.3 Local 192.168.0.49 static
Global 100.100.100.4 Local 192.168.0.48 static
Global 100.100.100.5 Local 192.168.0.107 static
Global 100.100.100.6 Local 192.168.0.47 static
Global 100.100.100.7 Local 192.168.0.46 static