Cisco ESA C390 Resource Conservation mode

[MohdZulFahmiHassan06801]

Hi

can any one help me how  avoid resource conversion mode for cisco esa c390.

when the memory hits 45% it will go resource conversion mode. and when that happen email will send/receive slow. Many email will go for queue.

is there any work around to increase memory from 45% to 75% manually?

Regards.

[SriramV]

ESA will enter into Resource Conservation mode when Mem usage goes more than 75%

there is no one reason for that.

Cisco ESA C390 Resource Conservation mode

Request to check TAC to analyze the ESA stats and ESA config.

you can also try reversing any recent config change. 

[MohdZulFahmiHassan06801]

Hi SriramV

Thank you for replay, but as i see when the memory is at 45% it will enter resource mode and not 75%. how to increase the memory to 75% then enter to resource mode? Is there something wrong with the hardware as the memory after reaching 45% and could not drop/fluctuate.

let me share with you resource info, the email blast was very slow and I need to reboot the appliance to make it back to normal.

Before reboot
Mail Processing Queue
Current Incoming Connections:        12
Current Outgoing Connections:        16
         
Active Messages in Work Queue:        0
Active Messages in Quarantine:        0
Active Destination Objects in Memory:        3,004
 
Active Recipients in Queue
Unattempted:        3,007
Attempted:        135
Total Active Recipients:        3,142
 
Queue Space
Queue Space Used by Quarantine:        0B
Total Queue Space Used:        77.8MB
Total Queue Utilization:        0.2%
CPU Utilization
Email Security Appliance:        13.0%
Anti-Virus:        2.0%
Reporting:        0.0%
Quarantine:        0.0%
Overall CPU load average:        13.0%
 
General Resource Utilization
RAM Utilization:        45.0%
Disk I/O Utilization:        0.0%

---------------------------------------------------------------
After reboot
Mail Processing Queue
Current Incoming Connections:        2
Current Outgoing Connections:        82
         
Active Messages in Work Queue:        1
Active Messages in Quarantine:        0
Active Destination Objects in Memory:        1,718
 
Active Recipients in Queue
Unattempted:        3,209
Attempted:        1,557
Total Active Recipients:        4,766
 
Queue Space
Queue Space Used by Quarantine:        0B
Total Queue Space Used:        110.3MB
Total Queue Utilization:        0.3%
CPU Utilization
Email Security Appliance:        15.0%
Anti-Virus:        25.0%
Reporting:        0.0%
Quarantine:        0.0%
Overall CPU load average:        25.0%
 
General Resource Utilization
RAM Utilization:        1.0%
Disk I/O Utilization:        1.0%

[Mathew Huynh]

Hey,

I would definitely suggest having a CLI access and doing status detail output when you see this; this should allow us to see the ResCon value. ResCon shouldn't trigger and tarpit until higher unless it was configured low.

You can check the tarpit configuration on the CLI with tarpit (hidden command).

--

c690.esa121.lab (SERVICE)> tarpit

The system will slow down receiving when memory is low.
The system will begin resource conservation at 45% of memory usage.
The system will begin refusing mail at 60% of memory usage.

Choose the operation you want to perform:
- SETUP - Enable or disable tarpitting.
[]>

---

If you have it configured like I do in my lab here - it means it needs to be updated most likely.

To:

The system will slow down receiving when memory is low.
The system will begin resource conservation at 75% of memory usage.
The system will begin refusing mail at 85% of memory usage.

Choose the operation you want to perform:
- SETUP - Enable or disable tarpitting.
- CLUSTERSET - Set how tarpitting is configured in a cluster.
- CLUSTERSHOW - Display how tarpitting is configured in a cluster.
[]>

Thanks,

Mathew