Jeff,

If any session tries to access a pix when the pix is busy writing updates to memory done

by some another session, it asks the other session to wait for some time so that it writes the changes to memory and loads full configuration for any more sessions. This is a normal behaviour.

Some times it takes too long depending on the traffic load at the time while the PIX is

still trying to save the configuration. Just wait until it finishes writing and/or

disconnect ethernet interfaces to reduce cpu load.

If you still suspect a PIX hang a reload normally clears the problem, however all config changes may be lost since the last saved update and you will have to enter the changes again.

Regards,

Arul

*Pls rate if it helps*